2020 Scrum Guide Flashcards
1
Q
What decade was Scrum developed in?
A
Early 1990s
2
Q
When was the first version of the Scrum Guide written?
A
2010
3
Q
What is the purpose of the Scrum Guide?
A
- definition of Scrum
- all elements explained and serve a specific purpose - can’t take any out
4
Q
What do “developers” encompass in a general sense in terms of Scrum?
A
Anyone who gets value from Scrum
5
Q
Give the definiton of Scrum
A
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems
6
Q
In a nutshell, what sort of environment does Scrum require a Scrum Master to foster?
A
- A Product Owner orders the work for a complex problem into a Product Backlog.
- The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
- The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
- Repeat
7
Q
Why is the Scrum framework purposefully incomplete, only defining the parts required to implement Scrum theory?
A
- Scrum is built upon by the collective intelligence of the people using it.
- No detailed in instructions –> rules of Scrum guide their relationships and interactions.
- make the desired result of management, environment and work techniques visible so improvements can be made.
8
Q
What is Scrum founded on?
A
- empiricism
- lean thinking
9
Q
What does empiricism assert?
A
Knowledge comes from experience and making decisions based on what is observed
10
Q
What is the benefit of lean thinking?
A
Reduces waste and focuses on the essentials
11
Q
What sort of approach does Scrum employ?
A
Scrum employs an iterative, incremental approach
12
Q
Why does Scrum employ an iterative, incremental approach?
A
To optimized predictability and to control risk
13
Q
What type of groups of people does Scrum engage?
A
groups of people who collectively have all the skills and expertise to do the work and share or acquire such skills as needed
14
Q
How many formal events does Scrum have?
A
4
15
Q
What is the overall purpose of combining the four formal Scrum events?
A
for inspection and adaptation within a containing event, the Sprint
16
Q
Why do the four Scrum events work?
A
they implement the empirical Scrum pillars of transparency, inspection, and adaptation
17
Q
What are the Scrum pillars?
A
- Transparency
- Inspection
- Adaption
18
Q
Why is transparency a pillar of Scrum?
A
- The emergent process and work must be visible to those performing the work as well as those receiving the work.
- important decisions are based on the perceived state of its three formal artifacts.
- Artifacts that have low transparency can lead to decisions that diminish value and increase risk.
19
Q
What does transparency enable in Scrum?
A
Transparency enables inspection
20
Q
What is inspection without transparency?
A
Misleading and wasteful
21
Q
What role does inspection in Scrum?
A
Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems
22
Q
What does Scrum provided to help with inspection?
A
cadence in the form of its five events
23
Q
What does inspection enable?
A
Adaptation
24
Q
What are Scrum events desired to provoke?
A
change
25
What role does adaption play in Scrum?
If any aspects of a process deviate outside acceptable limits or if the resulting product is unacceptable, the process being applied or the materials being produced must be adjusted.
The adjustment must be made as soon as possible to minimize further deviation.
26
When does adaptation become difficult in Scrum?
when the people involved are not empowered or self-managing
27
When is a Scrum team expected to adapt?
the moment it learns anything new through inspection
28
What are the five scrum values?
Commitment
Focus
Openness
Respect
Courage
29
What does the Scrum Team commit to?
achieving its goals and to supporting each other
30
What is the Scrum Team's primary focus?
the work of the Sprint to make the best possible progress toward their goals
31
What are the Scrum Team open about?
the work and the challenges
32
Comment on the Scrum Value "respect" in Scrum
Scrum Team members respect each other to be capable, independent people, and are respected as such by the people with whom they work
33
What does a Scrum team have courage for?
courage to do the right thing, to work on tough problems
34
What do the five scrum values give direction to?
Scrum Team's work, actions and behaviour
35
What reinforces Scrum Values in Scrum?
The decisions that are made, the steps taken, and the way Scrum is used
36
How is trust build via the Scrum Values?
When these values are embodied by the Scrum Team and the people they work with, the empirical Scrum pillars of transparency, inspection, and adaptation come to life building trust
37
Who does the Scrum Team consist of?
1 Scrum Master
1 Product Owner
Developers
38
Are there any sub-teams or hierarchies in a Scrum Team?
No
39
What is the Scrum Team focused on?
one objective at a time, the Product Goal
40
Define cross-functional
all members have all the skills necessary to create value each Sprint
41
Define self-managing
all members internally decide who does what, when and how
42
How many people in a Scrum team? Why?
10 or fewer
small enough to remain nimble and large enough to complete significant work within a Sprint
43
What happens when a Scrum Team becomes too large
They consider reorganising into multiple cohesive Scrum Teams, each focused on the same product
44
When a Scrum Team gets too big and splits into multiple teams, do the share the same Product Goal, Product Backlog and PO?
Yes - same Product Goal, Product Backlog and Product Owner
45
What activities are the Scrum team responsible for?
All product-related activities from stakeholder collaboration, verification, maintenance, operation, experiementation, research and development, and anything else that might be required
46
Comment on the pace of a Scrum Team
Sustainable , which improves the team's focus and consistency
47
What is the entire Scrum Team accountable for?
Creating a valuable, useful Increment every Sprint
48
What three accountabilities does Scrum define within a Scrum Team?
Developers
Product Owner
Scrum Master
49
Define Developers
People in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint
50
What will Developers always be accountable for?(4)
- Creating a plan for the sprint, the Sprint Backlog.
- Instilling quality by adhering to a Definition of Done.
- Adapting their plan each day toward the Sprint Goal.
- Holding each other accountable as professionals.
51
What is the key thing that the Product Owner accountable for?
maximizing the value of the product resulting from the work of the Scrum Team
52
Aside from maximising the product value, what is the Product Owner accountable for?
effective Product Backlog management
53
What does effective Product Backlog management include, done by the PO?
- Developing and explicitly communicating the Product Goal
- Creating and clearly communicating Product Backlog items
- Ordering Product Backlog items
- Ensuring that the Product Backlog is transparent, visible and understood
54
Is the Product Owner allowed to delegate the four tasks for effective Product Backlog refinement?
Yes, they can delegate the responsibilities to others. BUT, the PO remains accountable
55
For the Product Owner to succeed, who must respect their decisions?
The entire organisation
56
Where are a Product Owner's decisions reflected?
Their decisions are visible in the content and the ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review
57
Is the Product Owner one person or a committee?
PO is one person
58
What may a Product Owner represent?
They may represent the needs of many stakeholders in the Product Owner
59
If someone wants to change the Product Backlog and they are no the PO, what must they do?
Try convince the PO
60
What is the Scrum Master accountable for?
Establishing Scrum as defined in the Scrum Guide
61
How does a Scrum Master establish Scrum as defined in the Scrum Guide?
Help everyone understand Scrum theory and practice, both with the Scrum Team and the organisation
62
What is the Scrum Master accountable for?
The Scrum Team's effectiveness
63
Does the Scrum Master improve the Scrum Team's effectiveness?
By enabling the Scrum Team to improve its practices, within the Scrum framework
64
Scrum Masters are true leaders. Who do they serve?
They server the Scrum Team and the larger organisation
65
What four (of many) ways does the Scrum Master serve the Scrum Team, as mentioned in the Scrum Guide?
1. Coaching the team members in self-management and cross-functionality
2. Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done
3. Causing the removal of impediments to the Scrum Team’s progress
4. Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox
66
What four (of many) ways does the Scrum Master serve the Product Owner, as mentioned in the Scrum Guide?
1. Helping find techniques for effective Product Goal definition and Product Backlog management
2. Helping the Scrum Team understand the need for clear and concise Product Backlog items
3. Helping establish empirical product planning for a complex environment
4. Facilitating stakeholder collaboration as requested or needed
67
What four (of many) ways does the Scrum Master serve the organisation, as mentioned in the Scrum Guide?
1. Leading, training, and coaching the organization in its Scrum adoption;
2. Planning and advising Scrum implementations within the organization;
3. Helping employees and stakeholders understand and enact an empirical approach for complex work;
4. Removing barriers between stakeholders and Scrum Teams.
68
What is a Sprint a container for?
All other events
69
What are each event in Scrum a formal opportunity for?
Inspecting and adapting Scrum artifacts
70
What are Scrum events specifically designed to enable?
Transaprency
71
Failure to operate any Scrum events prescribed results in what?
Lost opportunities to inspect and adapt
72
Events are used in Scrum to create ______ and minimize ____
create regularity
minimize the need for meetings not defined in Scrum
73
Optimally, all Scrum events are held at the same time and place. Why?
To reduce complexity
74
Are Sprints fixed length?
Yes
75
How long are Sprints?
One month or less
76
Why are Sprints one month or less and fixed length?
To create consistency
77
When does a new Sprint start?
Immediately after the conclusion of the previous Sprint
78
What key things happen within a Sprint?
All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective
79
During the Sprint, can changes be made that may endanger the Sprint Goal?
No
No changes are made that would endanger the Sprint Goal
80
During the Sprint, does quality decrease?
No
Quality does not decrease
81
During the Sprint, can the Product Backlog be refined?
Yes, the Product Backlog is refined as needed
82
During the Sprint, can the scope be clarified and renegotiated?
Yes, the scope may be clarified and renegotiated with the Product Owner as more is learned
83
How do Sprints enable predictability?
By ensuring inspection and adaption of progress toward a Sprint Goal at least every calendar month
84
When a Sprint's horizon is too long, what happens?
- Sprint Goal may become invalid
- complexity may rise
- risk may increase
85
Shorter Sprints can be employed to achieve what?
- generate more learning cycles
- limit risk of cost and effort to a smaller time frame
86
Can each Sprint be thought of as a short project?
Yes
87
Various practices exists to forecast progress, like burn-downs, burn-ups, or cumulative flows. Do they replace the important of empiricism?
No!
88
Can we make predictions in complex environments?
No, what will happen is unknown
89
What can be used for forward-looking decision making?
Only what has already happened
90
When can a Sprint be cancelled?
If the Sprint Goal becomes obsolete
91
Who has the authority to cancel the Sprint?
Product Owner
92
What does Sprint Planning initiate?
the Sprint
93
How does Sprint Planning initiate the Sprint?
By laying out the work to be performed for the Sprint
94
How is the resulting planning from the Sprint Planning created?
By the collective work of the entire Scrum Team
95
Who ensures that the Sprint Planning attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal?
Product Owner
96
What must the Product Owner have prepared for before the Sprint Planning event starts?
That attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal
97
Can people external to the Scrum Team attend Sprint Planning?
Yes, if the Scrum Team invites them so they can provide advice
98
What three topics does Sprint Planning address?
1. Why is this Sprint valuable?
2. What can be Done this Sprint?
3. How will the chosen work get done?
99
What happens during the "WHY" part of Sprint Planning? i.e. 'why is this sprint valuable?
- The Product Owner proposes how the product could increase its value and utility in the current Sprint.
The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders.
100
When must the Sprint Goal be finalized by?
The end of Sprint Planning
101
What happens during the 'WHAT' part of Sprint Planning?
- Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint.
- The Scrum Team may refine these items during this process.
102
What is increased when the Scrum Team refines Product Backlog items further during Sprint Planning?
understanding and confidence
103
What can Developers do to increase their understanding of how much work they can take into a Sprint? i.e. their Sprint forecast
Get a good understanding of their past performance, upcoming capacity and DoD
104
What happens in the 'HOW' part of Sprint Planning?
- For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done
--> decompose to smaller items
- Sprint backlog formed
105
How do Developers often plan the work necessary to create an Increment that meets the Definition of Done?
by decomposing Product Backlog items into smaller work items of one day or less.
How this is done is at the sole discretion of the Developers.
106
Who decides how Product Backlog items are decomposed?
Developers - no one else
107
What makes up the Sprint Backlog?
- Sprint Goal
- Product Backlog items selected for the Sprint
- plan for delivering them
108
Is Sprint Planning time boxed?
Yes
109
How long is Sprint Planning timeboxed for?
maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
110
What is the purpose of the Daily Scrum?
Inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planning work
111
How long is the Daily Scrum for?
15 minutes
112
Who is the Daily Scrum intended for?
Developers of the Scrum Team
113
Why is the Daily Scrum held at the same time and place every working day of the Sprint?
To reduce complexity
114
Does the Product Owner or Scrum Master attend the Daily Scrum?
If they are actively working on items in the Sprint Backlog, then they participates as Developers
115
Does it matter what structure and techniques are used in the Daily Scrum?
No
Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work
116
What aspect of the Daily Scrum creates focus and improves self-management?
Allowing Developers to choose the structure and techniques which help them focus on progress towards the Sprint Goal and product an actional plan for the next day of work
117
What are four of the benefits of Daily Scrums
(1) improve communication
(2) identify impediments
(3) promote quick decision making
(4) eliminate the need for other meetings
118
When can Developers adjust their plan during the Sprint?
(1) Daily Scrum
(2) When they meet throughout the day for more detailed discussions about adapting or-replanning the rest of the Sprint's work
119
Are Developers allowed to adjust their plan outside of stand up?
Yes
120
What is the purpose of the Sprint Review?
to inspect the outcome of the Sprint and determine future adaptations
121
Who presents what during the Sprint Review? What happens next?
The Scrum Team presents the results of their work to key stakeholders.
Progress toward the Product Goal is discussed
122
Who must attend a Sprint Review?
Scrum Team and stakeholders
123
What do the Scrum Team and stakeholders review during the Sprint Review?
what was accomplished in the Sprint and what has changed in their environment
124
What do attendees of the Sprint Review do with the info of what has been accomplished and what has change in their environment?
Attends collaborate on what to do next
125
What may get adjusted based on the findings from what was accomplished in the Sprint and what has changed in the environment?
The Product Backlog - may be adjusted to meet new opportunities
126
What should the Scrum Team avoid and why during the Sprint Review?
Avoid limiting it to a presentation.
It is supposed to be a working session
127
When does the Sprint Review occur during the Sprint?
Second to last event
128
How long is the Sprint Review timeboxed for?
For ours for a one-month Sprint.
For shorter Sprints, it is usually shorter
129
What is the purpose of the Sprint Retrospective?
To plan ways to increase quality and effectiveness
130
What does the Scrum Team inspect during the Sprint Retrospective?(5)
They inspect how the last Sprint went regards to
(1) individuals
(2) interactions
(3) process
(4) tools
(5) their Definition of Done
131
Comment on what things are discussed regarding assumptions during the Sprint Retrospective
Assumptions that led them astray are identified and their origins explored
132
What are the three common things that should be discussed during the Sprint Retrospective?
(1) what went well during the Sprint
(2) what problems the Scrum Teams encountered
(3) how those problems were (or were not) solved
133
The Scrum Guide doesn't explictly say "Action Items" but implies these. Explain what this means
- 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 (but not mandatory)
134
What event concludes the Sprint?
Sprint Retrospective
135
How long is the Sprint Retrospective Timeboxed for?
Three hours for a one-month Sprint.
For shorter Sprints, the event is usually shorter
136
What does Scrum's artifacts represent?
work or value
137
What are Scrum Artifacts designed for?
Maximising transparency of key info
- thus everyone inspecting them has the same basis for adaptation
138
What does each Scrum artifact contain? What does it ensure?
A commitment
Ensures it provides info that enhances transparency and focus against which progress can be measured
139
How many Scrum Artifacts are there? Name them
3
(1) Product Backlog
(2) Sprint Backlog
(3) Increment
140
What is the commitment of the Product Backlog?
Product Goal
141
What is the commitment for the Sprint Backlog?
Sprint Goal
142
What is the commitment of the Increment?
Definition of Done
143
What do the commitments of the three Scrum artifacts exists to reinforce?
Empiricism and the Scrum Values for the Scrum Team and their stakeholders
144
What is the Product Backlog?
An emergent, ordered list of what is needed to improve the product.
It is the single source of work undertaken by the Scrum Team
145
When are Product Backlog items deemed ready for selection in a Sprint Planning event?
when they can be Done by the Scrum Team within one Sprint
146
When do Product Backlog items acquire the right degree of transparency?
After refining activities
147
Is refinement a Scrum Activity?
No - no fixed frequency, duration etc.
148
What is Product Backlog refinement?
the act of breaking down and further defining Product Backlog items into smaller more precise items
- adding details such as a description, order and size
- attributes vary with the domain of work
149
Is Product Backlog refinementa one off or an ongoing activity?
Ongoing
150
Who are responsible for sizing Product Backlog items?
The Developers who will be doing the work
151
How can the Product Owner influence the Developers when they are doing Product Backlog refinement to size the items?
Help them understand and select trade-offs
152
What is the Product Goal?
It describes a future state of the product which can serve as a target for the Scrum Team to plan against
153
Where does the Product Goal reside?
In the Product Backlog
154
Aside from the Product Goal which is in the Product Backlog, what does the rest of the Product Backlog emerge to define?
The "WHAT" will fulfill the Product Goal
155
A product is a vehicle to deliver what?
value
156
How is a product defined in Scrum?
(1) vehicle to deliver value
(2) clear boundary, known stakeholders, well-defined users or customers
(3) could be a service, physical product, or something more abstract
157
What is the long-term objective for the Scrum Team?
Product Goal
158
When can a Scrum Team move onto another Product Goal?
when they fulfill (or abandon) the existing Product Goal
159
What are the three parts of the Sprint Backlog?
- why --> Sprint Goal
- what --> subset of Product Backlog Items for the Sprint
- how --> actionable plan for delivering the Increment
160
Who makes the Sprint Backlog and who is it plan for
By the Developers for the Developers
161
What is the Sprint Backlog?
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
162
Can the Sprint Backlog be updated during the Sprint? If so, when?
Yes, throughout the Sprint as more is learned
163
How much detail should the Sprint Backlog have?
Enough that the Scrum Team can inspect their progress in the Daily Scum
164
What is the Sprint Goal?
single objective for the Sprint
165
Who commits to the Sprint Goal?
Developers
166
Comment on the flexibility of the Sprint Goal
provides flexibility in terms of the exact work needed to achieve it
167
What does the Sprint Goal create and resultantly encourage?
Creates coherence and focus
Encouraging the Scrum Team to work together rather than on separate initiatives
168
When is the Sprint Goal created?
During the Sprint Planning event
169
Where does the Sprint Goal get added after being created?
To the Sprint Backlog
170
Can the scope of the Sprint Goal be changed during the sprint? How?
Yes
Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal
171
What is an Increment?
a concrete stepping stone toward the Product Goal
172
Comment on how all Increments work together
Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together
173
In order to provide value, the Increment must be ___
usable
174
How many Increments may be created within a Sprint?
Multiple
175
When multiple Increments are created within a Sprint, how many are presented during the Sprint Review? Why?
All of them - to support empiricism
176
Can an increment be delivered to stakeholders prior to the end of the Sprint?
Yes
177
Is the Sprint Review a gateway to releasing value
No
178
When is work considered part of an Increment?
When it meets the Definition of Done
179
What is the Definition of Done?
a formal description of the state of the Increment when it meets the quality measures required for the product
180
When is an Increment born?
The moment a Product Backlog item meets the Definition of Done
181
How does the Definition of Done create transparency?
by providing everyone a shared understanding of what work was completed as part of the Increment
182
If a Product Backlog item does not meet the Definition of Done can it be released?
No
183
If a Product Backlog item does not meet the Definition of Done, can it be presented at the Sprint Review?
No
184
What happens if a Product Backlog item does not meet the Definition of Done?
it returns to the Product Backlog for future consideration
185
If the Definition of Done for an increment is part of the standards of the organization, what does this mean for Scrum Teams?
they must follow it as a minimum
186
If the Definition of Done for an increment is NOT part of the standards of the organization, what must a team do?
Scrum Team must create a Definition of Done appropriate for the product
187
Who are required to conform to the Definition of Done?
Developers
188
What happens if there are multiple Scrum Teams working together on a product when it comes to the Definition of Done?
they must mutually define and comply with the same Definition of Done
