Welcome to the Organizational Agile Assessment. Please answer all the questions and hit submit at the end. The summary of the results will be presented in the training class.

1. 

What is your overall assessment of the current state of your Agile implementation?

2. 

If there is one area that would have the largest impact on your Agile maturity, what would it be?

3. 

What has been the biggest benefit to you and/or the organization from moving to an Agile development approach?

4. 

You consistently deliver working, tested software every 30 days or less

5. 

Each release is driven by business need

6. 

Each Sprint you are continuously improving

7. 

The Teams are having fun and there is a high energy level

8. 

The Team presents their own work at the Sprint Review

9. 

Overtime is rare and happens voluntarily

10. 

Discussing, criticizing, and experimenting with the process is welcome

11. 

There is a clearly defined Product Owner role

12. 

The Product Owner is empowered to prioritize the product backlog

13. 

The Product Owner has direct contact with customer

14. 

The Product Owner is actively involved throughout each Sprint

15. 

The Product Owner has direct contact with the Team

16. 

There is a clearly defined Scrum Master role

17. 

The Team works off of a Sprint backlog

18. 

The Sprint backlog is visible to any stakeholder

19. 

The Team updates the Sprint Backlog daily

20. 

Stakeholders attend the Sprint Review

21. 

Team Members raise impediments at the Daily Scrum

22. 

The Definition of Done is met for every completed User Story when applicable

23. 

The Team actively participates in the Sprint Retrospective

24. 

Backlog grooming occurs every Sprint

25. 

The estimates in the product backlog are given by the Team

26. 

The output of the Sprint Planning meeting is a realistic Sprint backlog that the Team agrees is doable

27. 

Estimates are given in relative size (e.g. Story Points) rather than hours

28. 

A Sprint planning meeting occurs every Sprint

29. 

Sprints are not interrupted by unplanned work outside of the Sprint Backlog

30. 

The Team usually delivers what they commit to on the Sprint Backlog

31. 

The Team's historical Velocity is used for Sprint Planning

32. 

Scrum Masters are seen as servant leaders, not managers

33. 

The Team consistently answers the 3 questions

34. 

Each team has a Definition of Done

35. 

Only completed Stories are presented at the Sprint Review

36. 

Everyone stands up at the Daily Scrum

37. 

Retrospectives are held after every Sprint

38. 

Many of the improvements identified in the retrospective are implemented in the next Sprint

39. 

The Product Owner maintains a product backlog at least one Sprint ahead of the Team

40. 

The whole team and the Product Owner attend the Sprint Planning meeting

41. 

Each Sprint is no longer than 30 days

42. 

Each Sprint for a project is the same length

43. 

The Team sits together during the Sprint

44. 

The Team is no larger than 9 people

45. 

The Team generally has all the skills required by the project

46. 

The Team members are able to step outside their role and be cross-functional

47. 

Acceptance tests are written in advance of development for most User Stories

48. 

The Product Owner writes the acceptance tests

49. 

The Team can modify the Sprint backlog during the Sprint to meet the Sprint Goal

50. 

The team tracks work remaining during the Sprint using a tool like Burndown Charts

51. 

Dependent Teams integrate during each Sprint

52. 

The Scrum Master is empowered to remove impediments for the Team

53. 

The Daily Scrum happens every day at the same time and place

54. 

All Team members participate in the Daily Scrum

55. 

The Daily Scrum is limited to 15 minutes

56. 

A Sprint Review happens every Sprint

57. 

Feedback is encouraged and captured at the Sprint Review

58. 

Automated unit testing is implemented where appropriate

59. 

Automated regression testing is implemented where appropriate

60. 

The Sprint Backlog and/or Burndown Charts are updated daily

61. 

Scrum artifacts (Backlogs and Burndown Charts) are visible to all project stakeholders

62. 

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

63. 

Dependent Teams have a “chief” Product Owner or similar role who is empowered to make product decisions across all product teams