Welcome to the Agile Maturity Assessment

You are about to answer 60 questions to assess your organization's Agile maturity. Once you complete them all, you will receive a weighted total score that will be aligned with an overall Agile Maturity Model. If you would like to have multiple people perform this exercise for your organization and receive an aggregated detailed analysis and recommendations, please contact us.

Name
Email for Results
1. You consistently deliver working, tested software every 30 days or less
2. Each release is driven by business need
3. Each Sprint you are continuously improving
4. The Teams are having fun and there is a high energy level
5. The Team presents their own work at the Sprint Review
6. Overtime is rare and happens voluntarily
7. Discussing, criticizing, and experimenting with the process is welcome
8. There is a clearly defined Product Owner role
9. The Product Owner is empowered to prioritize the product backlog
10. The Product Owner has direct contact with customer
11. The Product Owner is actively involved throughout each Sprint
12. The Product Owner has direct contact with the Team
13. There is a clearly defined Scrum Master role
14. The Team works off of a Sprint backlog
15. The Sprint backlog is visible to any stakeholder
16. The Team updates the Sprint Backlog daily
17. Stakeholders attend the Sprint Review
18. Team Members raise impediments at the Daily Scrum
19. The Definition of Done is met for every completed User Story when applicable
20. The Team actively participates in the Sprint Retrospective
21. Backlog grooming occurs every Sprint
22. The estimates in the product backlog are given by the Team
23. The output of the Sprint Planning meeting is a realistic Sprint backlog that the Team agrees is doable
24. Estimates are given in relative size (e.g. Story Points) rather than hours
25. A Sprint planning meeting occurs every Sprint
26. Sprints are not interrupted by unplanned work outside of the Sprint Backlog
27. The Team usually delivers what they commit to on the Sprint Backlog
28. The Team's historical Velocity is used for Sprint Planning
29. Scrum Masters are seen as servant leaders, not managers
30. The Team consistently answers the 3 questions
31. Each team has a Definition of Done
32. Only completed Stories are presented at the Sprint Review
33. Everyone stands up at the Daily Scrum
34. Retrospectives are held after every Sprint
35. Many of the improvements identified in the retrospective are implemented in the next Sprint
36. The Product Owner maintains a product backlog at least one Sprint ahead of the Team
37. The whole team and the Product Owner attend the Sprint Planning meeting
38. Each Sprint is no longer than 30 days
39. Each Sprint for a project is the same length
40. The Team sits together during the Sprint
41. The Team size is between 3 and 9 people.
42. The Team generally has all the skills required by the project
43. The Team members are able to step outside their role and be cross-functional
44. Acceptance tests are written in advance of development for most User Stories
45. The Product Owner writes the acceptance tests
46. The Team can modify the Sprint backlog during the Sprint to meet the Sprint Goal
47. The team tracks work remaining during the Sprint using a tool like Burndown Charts
48. Dependent Teams integrate during each Sprint
49. The Scrum Master is empowered to remove impediments for the Team
50. The Daily Scrum happens every day at the same time and place
51. All Team members participate in the Daily Scrum
52. The Daily Scrum is limited to 15 minutes
53. A Sprint Review happens every Sprint
54. Feedback is encouraged and captured at the Sprint Review
55. Automated unit testing is implemented where appropriate
56. Automated regression testing is implemented where appropriate
57. The Sprint Backlog and/or Burndown Charts are updated daily
58. Scrum artifacts (Backlogs and Burndown Charts) are visible to all project stakeholders
59. Dependent Teams (a team working on the same project as other teams) are meeting together weekly to manage dependencies, e.g. Scrum of Scrums or similar
60. Dependent Teams have a “chief” Product Owner or similar role who is empowered to make product decisions across all product teams

Copyright Notice 2018.

Unless otherwise noted, these materials and the presentation of them are based on the methodology developed by Cape Project Management, Inc. and are copyrighted materials of Cape Project Management, Inc., which are used with its permission. Cape Project Management, Inc. reserves all its rights. All other brand or product names used in this presentation are the trade names or registered trademarks of their respective owners. The Agile Maturity Matrix was adapted from original source: http://www.scribd.com/doc/105468803/Governance-for-Agile-Delivery The online Agile self-assessment was adapted from original source developed by Henrik Kniberg and is licensed under a Creative Commons: http://creativecommons.org/licenses/by-nc-nd/3.0/