YES/NO Things to Consider

1. Is a tool used to manage the Sprint Backlog?

[If Yes, please identify the tool(s)?]

2. Does the Team employ a Task Board?

[If Yes, is an electronic, physical, or both used?]

3. Is the Team estimating the Sprint Backlog using hours?

[If No, what value is the Team using the estimate the Sprint Backlog?]

4. Does the Team assume responsibility for adding Tasks to the Sprint Backlog?

[If No, who currently applies updates to the Sprint Backlog?]

5. What information is captured in the Sprint Backlog?

[Are any of the following tracked for Tasks in the Sprint Backlog: Task Definition, Task Owner, Original Estimated Hours, Estimated Hours Remaining, Is Task Blocked (Yes/No)?]

6. Is the Team currently allocating tasks to resources during Sprint Planning?

[If Yes, is the Team experiencing any challenges with self-organizing on the ownership of tasks?]

7. Who typically attends the Sprint Planning Meeting?

[Do the Product Owner and Delivery Team always participate in the Sprint Planning Meeting?]

8. What is the typical duration of the Sprint Planning Meeting?

[Is a standard format used for all Sprint Planning Meetings?]

9. Has the Team established a Velocity?

[If Yes, over how many Sprints has the Team maintained this Velocity?]

WHY? For in-place teams, the Scrum Master can quickly identify the

manner in which Sprints are being performed, and the survey also

captures the Sprint execution preferences of a new team.

Sprint

Planning

Survey

10. Is the Team collaborating with the Product Owner to establish a Goal for each Sprint?

[If Yes, how is the Team fairing in achieving the goals of the Sprints?]

11. Is the Team routinely conducting a Sprint Review?

[If Yes, what is the format of the Sprint Review?

Do any Distributed Team Members participate in the Sprint Review?

Is the Product Owner and other Stakeholders always present at the Sprint Review?]

12. What is the typical duration of your Sprint Reviews?

[If the duration is exceeds 1 hour, what is the rationale for having a Sprint Review of this length?]

13. When does the Team usually discuss the feedback received from the Sprint Review?

[Is this activity combined with Sprint Planning, Sprint Retrospective, other?]

14. Is the Sprint Plan posted in a central location?

[Is Yes, what is the location?]

15. What metrics are tracked for the Sprint?

[What reports are used to present these metrics?]

16. Is The Team generating Unit Test for code delivered in each Sprint?

[If Yes, are the Unit Test automated?

Are the estimated hours for the Unit Test task explicitly stated in the Sprint Plan?]

17. Is The Team including estimates for Team Meetings in the Sprint Plan?

[If Yes, is the Meeting Preparation & Execution been tracked as a single task or broken into separate tasks for each team member?]

18. Does The Team employ a Commitment-Driven or Velocity-Driven approach for Sprint Planning?

[Is the Team informed about the differences between these two approaches?]

19. Does The Team have any Support and/or Maintenance responsibilities?

[If Yes, is the amount of effort for these activities being estimated per each Sprint?

How often is the Resource Capacity of The Team revised?]