| A | B | C | D | E | |
|---|---|---|---|---|---|
1 |  | ||||
2 | Scrum Scorecard | ||||
3 | |||||
4 | Instructions | ||||
5 | Make your own working copy of this document by clicking File > Make a copy, or you can download it by clicking File > Download. | ||||
6 | |||||
7 | Think about the overall health of your team. How much do you agree with the following statements? | ||||
8 | |||||
9 | |||||
10 | Statement | Your Answer | Score | ||
11 | 1) | The team's progress is visible to the team and its stakeholders. | | ||
12 | |||||
13 | 2) | The team frequently inspects their work progress and scrum processes and adjusts them when they can be improved. | | ||
14 | |||||
15 | 3) | The scrum team commits to achieving its goals and to supporting each other. | | ||
16 | |||||
17 | 4) | The team's primary focus is on the work of the sprint to make the best possible progress toward their goals. | | ||
18 | |||||
19 | 5) | The scrum team and its stakeholders are open about the work and its challenges. | | ||
20 | |||||
21 | 6) | Scrum team members respect each other to be capable, independent people, and are respected as such by the people with whom they work. | | ||
22 | |||||
23 | 7) | The scrum team members have the courage to do the right thing, to work on tough problems. | | ||
24 | |||||
25 | 8) | The scrum team consists of one scrum master, one product owner, and developers. | | ||
26 | |||||
27 | 9) | Within a scrum team, there are no sub-teams or hierarchies. | | ||
28 | |||||
29 | 10) | The scrum team is a cohesive unit of professionals focused on one objective at a time: the product goal. | | ||
30 | |||||
31 | 11) | Scrum teams are cross-functional, meaning the members have all the skills necessary to create value each sprint. | | ||
32 | |||||
33 | 12) | Scrum teams are self-managing, meaning they internally decide who does what, when, and how. | | ||
34 | |||||
35 | 13) | The scrum team is small enough to remain nimble and large enough to complete significant work within a sprint, typically 10 or fewer people. | | ||
36 | |||||
37 | 14) | The developers are always accountable for creating a plan for the sprint, for instilling quality by adhering to a definition of done, for adapting their plan each day toward the sprint goal, and for holding each other accountable as professionals. | | ||
38 | |||||
39 | 15) | The product owner is accountable for maximizing the value of the product through effective product backlog management, which includes developing and explicitly communicating the product goal, creating and clearly communicating product backlog items, ordering product backlog items, and ensuring that the product backlog is transparent, visible and understood. | | ||
40 | |||||
41 | 16) | The entire organization respects the product owner's decisions. | | ||
42 | |||||
43 | 17) | The product owner is one person, not a committee. Those wanting to change the product backlog can do so by trying to convince the product owner. | | ||
44 | |||||
45 | 18) | Scrum masters are true leaders who serve the scrum team and the larger organization. | | ||
46 | |||||
47 | 19) | The scrum master coaches scrum team members in self-management and cross-functionality, helps the scrum team focus on creating high-value Increments that meet the definition of done, causes the removal of impediments to the scrum team’s progress, and ensures that all scrum events take place and are positive, productive, and kept within the timebox. | | ||
48 | |||||
49 | 20) | The scrum master helps the product owner find techniques for effective product goal definition and product backlog management, helps the scrum team understand the need for clear and concise product backlog items, helps establish empirical product planning for a complex environment, and facilitates stakeholder collaboration as requested or needed. | | ||
50 | |||||
51 | 21) | The scrum master leads, trains, and coaches the organization in its scrum adoption, planning and advising scrum implementations within the organization, helping employees and stakeholders understand and enact an empirical approach for complex work, and removing barriers between stakeholders and scrum teams. | | ||
52 | |||||
53 | 22) | Sprints are fixed length events of one month or less. A new sprint starts immediately after the conclusion of the previous sprint. | | ||
54 | |||||
55 | 23) | During the sprint, no changes are made that would endanger the sprint goal, quality does not decrease, the product backlog is refined as needed, and scope may be clarified and renegotiated with the product owner as more is learned. | | ||
56 | |||||
57 | 24) | Sprint planning covers the "why" (sprint goal) of the sprint, the "what" (sprint backlog), and the "how" (plan for the sprint). | | ||
58 | |||||
59 | 25) | The daily scrum is a 15-minute event for the developers of the scrum team. Daily scrum focuses on progress toward the sprint goal and produces an actionable plan for the next day of work. | | ||
60 | |||||
61 | 26) | Sprint reviews inspect the outcome of the sprint and determine future adaptations. The scrum team presents the results of their work to key stakeholders and progress toward the product goal is discussed. The sprint review is a working session and not a presentation. | | ||
62 | |||||
63 | 27) | In retros, the scrum team inspects how the last sprint went with regards to individuals, interactions, processes, tools, and their definition of done. The scrum team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the sprint backlog for the next sprint. | | ||
64 | |||||
65 | 28) | The product backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the scrum team. | | ||
66 | |||||
67 | 29) | The product goal describes a future state of the product which can serve as a target for the scrum team to plan against. The product goal is in the product backlog. The rest of the product backlog emerges to define “what” will fulfill the product goal. | | ||
68 | |||||
69 | 30) | The sprint backlog is a plan by and for the developers. It is a highly visible, real-time picture of the work that the developers plan to accomplish during the sprint in order to achieve the sprint goal. Consequently, the sprint backlog is updated throughout the sprint as more is learned. | | ||
70 | |||||
71 | 31) | The sprint goal is the single objective for the sprint. | | ||
72 | |||||
73 | 32) | The definition of done is a documented description of the state of the increment when it meets the quality measures required for the product. It's created by the team and their stakeholders and is updated when needed. | | ||
74 | |||||
75 | 33) | An increment (or multiple increments) are produced during the sprint that meet the DoD. | | ||
76 | |||||
77 | Total Score: | 0 | |||
78 | Grade: | ||||
79 | Learn more about scrum at AgileLearningLabs.com |