Agile maturity matrix Welcome to the agile maturity matrix. Who is this questionnaire for ?Anyone who wishes to evaluate his/her agile maturity or the agile maturiy of a team. How long does it take ?There is no time limit. However, it has been made to be short ( ~10 minutes ). How does it work ? 1 question with a maturity scale from 1 to 5 1 answer per question To go to the next question, click on Next. To go back to the previous question, click on Previous At the end of the questionnaire, a recap of the questions and answers is sent by e-mail Commit to some concrete actions to improve your weaknesses and/or strengthen your qualities Retake the questionnaire later to evaluate your progression Please enter your Name and Surname Please enter the email address that will receive the answers at the end Free information field (i.e your team's name) 1. Is the planification of developments decided in relation to a business value ? 1 (Never) 2 3 4 5 (Always) 2. Is error allowed without punishment ? 1 (Never) 2 3 4 5 (Always) 3. Is change accepted and exploited ? 1 (Never) 2 3 4 5 (Always) 4. Is the delivery of good quality and operational ? 1 (Never) 2 3 4 5 (Always) 5. Is the cooperation good between all the individuals involved with the work? 1 (Not at all) 2 3 4 5 (Absolutely) 6. Do you waste any code or documentation? 1 (Never) 2 3 4 5 (Often) 7. Do you improve or simplify your process ? 1 (Never) 2 3 4 5 (Continuously) 1 out of 5 8. Does the Product Owner (PO) define the priorities of the items in the product backlog ? 1 (Never) 2 3 4 5 (Always) 9. Is the product backlog refined at every iteration ? 1 (Never) 2 3 4 5 (Always) 10. Is the PO available to share his/her vision ? 1 (Never) 2 3 4 5 (Always) 11. Is your product created with it's end user's collaboration ? 1 (Never) 2 3 4 5 (Always) 12. Is your product assessed by it's end user ? 1 (Never) 2 3 4 5 (Always) 2 out of 5 13. Does everyone know easily the progress of the project and the product because the information is available and updated in real time ? 1 (Not at all) 2 3 4 5 (Absolutely) 14. Do the retrospectives generate concrete improvement actions ? 1 (Never) 2 3 4 5 (Always) 15. Is the product delivered as expected and of good quality ? 1 (Never) 2 3 4 5 (Always) 16. Are the expressions of needs ready enough to be developed at the start of the actual development work ? 1 (Never) 2 3 4 5 (Always) 3 out of 5 17. Does the team self-organize (sprint backlog, items estimation, decision making, recruitment, tools, processes, tasks, level of quality... etc.) ? 1 (Never) 2 3 4 5 (Always) 18. Can the team request the addition of a technical story to the PO when needed ? 1 (Never) 2 3 4 5 (Always) 19. Does the team improve itself ? 1 (Never) 2 3 4 5 (Continuously) 20. Are stakeholders learning from the team ? 1 (Never) 2 3 4 5 (Always) 4 out of 5 21. Does your iterations produce an increment of the product that is potentially deliverable ? 1 (Never) 2 3 4 5 (Always) 22. Are acceptance criteria transformed into executable functional tests ? 1 (Never) 2 3 4 5 (Always) 23. Is the technical debt reduced with each iteration ? 1 (Never) 2 3 4 5 (Always) 24. Do the developers perform code reviews ? 1 (Never) 2 3 4 5 (Always) 25. Do experts share their skills and train other team members ? 1 (Never) 2 3 4 5 (Constantly) 26. Is it easy to release frequently ? 1 (Not at all) 2 3 4 5 (Absolutely) 5 out of 5 To end the questionnaire and submit your answers, please click on SUBMIT. Time's up
