How Agile are you?
A quiz to determine your level of agility
Sign in to Google to save your progress. Learn more
Email *
Each release is driven by a business need *
Scrum artifacts (Backlogs and Burndown Charts) are visible to all project stakeholders *
Stakeholders attend the Sprint Review and give valuable feedback. *
There is a consistency in the delivery of tested software every 30 days or less *
Dependent Teams (teams working on the same backlog) are meeting together weekly to manage dependencies, e.g. Scrum of Scrums *
Integration tests are done before each review to ensure integrity. *
The Team sits together during the Sprint *
The whole team and the Product Owner attend the Sprint Planning meeting *
Discussing, criticizing, and experimenting with the process is welcome *
Automated regression testing is implemented where appropriate *
Automated unit testing is implemented where appropriate *
Acceptance criterias are part of the user stories and used throughout the sprint as a checklist. *
The Product Owner is empowered to prioritize the product backlog *
The Team generally has all the skills required by the project *
The Scrum Master is empowered to remove impediments for the Team *
The Team actively participates in the Sprint Retrospective *
Many of the improvements identified in the retrospective are implemented in the next Sprint *
Team Members raise impediments at the Daily Scrum which happens every day at the same time and place *
Overtime is rare and happens voluntarily *
The Team updates the Sprint Backlog daily *
The team tracks its own performance metrics daily *
Sprints are not interrupted by unplanned work outside of the Sprint Backlog *
The Definition of Done is met for every completed User Story when applicable *
The estimates in the product backlog are given by the Team *
Retrospectives are held after every Sprint *
Each Sprint for a product is the same length *
A Sprint Review happens every Sprint *
The Team presents their own work at the Sprint Review and feedback is incorporated in the product backlog *
The Product Owner has direct contact with customer and gets instant information on changes to make in the backlog or reschuffing priorities. *
The Product Owner incorporates the feedback of the team in the product backlog *
The output of the Sprint Planning meeting is a realistic Sprint backlog that the Team agrees is doable *
The Team usually delivers what they commit to in the Sprint Backlog *
Every sprint the team integrates their work with other dependent teams(if any) to have a systems review *
Backlog refinement occurs every Sprint *
The Product Owner maintains a priority User Stories with a high level of details in the Product Backlog. *
The Product Owner has direct and regular contact with the Team *
Submit
Clear form
This content is neither created nor endorsed by Google. Report Abuse - Terms of Service - Privacy Policy