The Scrum Guide: My Notes Flashcards
1
Q
Scrum (short definition)
A
A framework for developing, delivering, and sustaining complex products.
2
Q
What are the elements of Scrum
A
roles, events,artifacts and rules that bind them together.
3
Q
Who are Ken Schwaber and Jeff Sutherland?
A
The developers of Scrum.
4
Q
Scrum (long definition)
A
A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
5
Q
Mention three features of Scum
A
It is:
- Lightweight.
- Simple to Understand
- Difficult to master
6
Q
What type of framework is Scrum
A
A process framework
7
Q
When did Scrum begin to be used?
A
In the early 1990s
8
Q
What is NOT scrum?
A
It is not a process, technique or definitive method.
9
Q
What does Scrum make clear?
A
The relative efficacy of your product, the team and the working environment.
10
Q
What has scrum been used for? (5 items)
A
- Research and identify viable markets, technologies and product capabilities.
- Develop products and enhancements.
- Release products and enhancements, as frequently as many times per day.
- Develop and sustain Cloud and other operational environments for product use.
- Sustain and renew products.
11
Q
What has been developed using Scrum (9)?
A
Software, hardware,embedded software,networks of interacting function, autonomous vehicles, schools, government, marketing, organizations operation, etc.
12
Q
How has Scrum’s utility in dealing with complexity been proven?
A
As technology, marketing and environmental complexities have increased.
13
Q
In which types of knowledge has Scrum proved especially effective?
A
Iterative and incremental knowledge transfer
14
Q
What is the essence of Scrum?
A
A small team of people.
15
Q
What characteristics (2) do individual teams have?
A
They are highly flexible and adaptive.
16
Q
What do the words “develop” and “development” imply in the Scrum guide?
A
Complex work
17
Q
What is the foundation of Scrum?
A
Empirical process control theory or empiricism
18
Q
What does Empiricism say?
A
According to empiricism, knowledge comes from experience an making decisions based on what is known.
19
Q
How does Scrum control risk?
A
With an iterative, incremental approach.
20
Q
What is transparency?
A
It means that significant aspects of the process must be visible to those responsible for the outcome.
21
Q
What is inspection?
A
Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.
22
Q
How often should inspections be made?
A
Inspections should not be so frequent that it gets in the way of the work.
23
Q
What is adaptation?
A
If in an inspection, it is determined that one or more aspects of a process deviate outside acceptable limits and the resulting product will be unacceptable, the process or material being processed must be adjusted.
24
Q
Which are the four formal events for inspection and adaptation?
A
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
25
Which are the (5) values of Scrum?
```
Commitment
Courage
Focus
Openness
Respect
```
26
What are the (3) pillars of Scrum?
transparency
inspection
adaptation
27
Who are the members of the Scrum Team?
a Product Owner
Development Team
a Scrum Master
28
Which (2) characteristics do Scrum Teams have?
They are self-organizing and cross-functional.
29
What does it mean that a Scrum Team is Self-organizing?
The teams choose how best to accomplish their work.
30
What does it mean that a Scrum Team is Cross-functional?
The teams have all the competencies needed to accomplish the work without depending on others not part of the team.
31
What does the Scrum Team model optimize?
Flexibility, creativity and productivity.
32
How do the Scrum Teams deliver products?
Iteratively and incrementally, maximizing opportunities for feedback.
33
What is the advantage of having incremental deliveries of "Done" product?
It ensures a potentially useful version of the working product being always available.
34
What are the responsibilities of the Product Owner?
He is responsible for maximizing the value of the product resulting from work of the Development Team.
35
Is the resulting product value maximization always the same?
No, it may vary widely across organizations, Scrum Teams, and individuals.
36
Who is responsible for managing the Product Backlog?
The Product Owner is the sole person responsible for managing the Product Backlog.
37
What (5) tasks does the Product Backlog management process have?
1) Clearly expressing Product Backlog Items.
2) Ordering the items in the Product Backlog to beast achieve goals and missions.
3) Optimizing the value of the work the Development Team performs
4) Ensuring the Product Backlog is visible, transparent and clear to all, showing what the Scrum Team will work on next.
5) Ensuring the Development Team understands items in the Product Backlog.
38
Who can manage the Product Backlog?
The Product Owner, who can make the Development Team do it, but the Product Owner remains accountable.
39
Who, ultimately, is accountable for managing the Product Backlog?
The Product Owner, despite him/her being able to let/make the Development team do it.
40
How many people can be a Product's Product Owner?
Only one person, not a committee.
41
If someone in a committee, that is not the product owner, wants to change the Product Backlog, what can he/she do?
Those wanting to change a Product Backlog item's priority must address the Product Owner.
42
What is necessary to have the Product Owner succeed?
The entire organization must respect his/her decisions.
43
What is the work of the Development Team?
Delivering a potentially releasable increment of "Done" product at the end of each Sprint.
44
When is a "Done" increment required?
at the Sprint Review.
45
Who can create the Increment?
Only members of the Development Team
46
What does the organization empower the Development Team to do?
To organize and manage their own work.
47
What is the result of synergy in the Development Team?
The optimization of the Development Team's overall efficiency and effectiveness.
48
What are the (5) characteristics of Development Teams?
1) They are self-organizing.
2) They are cross-functional
3) There are not recognized titles for Development Team members.
4) There are no sub-teams in the Development Team.
5) Despite specialized skills had by individual Development Team members, accountability belongs to the Team as a whole.
49
What does it mean that a Development Team is self-organizing?
It means that no one, not even the Scrum Master, tells the Development Team how to turn a Product Backlog into increments of potentially releasable functionality.
50
What does it mean that Development Teams are cross-functional?
that they have all the skills as a team to create a product increment.
51
What is the ideal size for a Development Team?
It should be small enough to remain nimble and large enough to complete significant work within a Sprint.
52
What happens with Development Teams with fewer than three members?
Interaction is decreased and it results in smaller productivity gains.
53
What can happen with small teams regarding skills?
Smaller Development Teams may encounter skill constraints during the Sprint, causing inability to deliver a potentially releasable increment.
54
What can happen with teams of more than nine members?
It requires too much coordination.
55
What is the result of large development teams?
Too much complexity is caused for an empirical process to be useful.
56
Are Product Owner and Scrum Master roles counted in the Development Team?
No, unless they are also executing the work of the Sprint Backlog.
57
What is the Scrum Master responsible for?
Promoting and supporting Scrum as defined in the Scrum Guide.
58
What does the Scrum Master do to promote and support Scrum?
Helping everyone understand Scrum theory, practices, rules and values.
59
Who is a servant-leader in Scrum?
The Scrum Master is a servant-leader for the Scrum Team
60
What does the Scrum Master do with those outside the Scrum Team?
He/she helps them understand which of their interactions with the Scrum Team are helpful and which aren't.
61
In which (7) ways does the Scrum Master serve the Product Owner?
1) Ensuring that goals, scope and product domain are understood as well as possible.
2) Finding techniques for effective Product Backlog management.
3) Helping the Scrum Team understand the need for clear and consice Product Backlog Items.
4) Understanding product planning in an empirical environment.
5) Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value.
6) Understanding and practicing agility
7) Facilitating Scrum events as requested or needed.
62
In which (5) ways does the Scrum Master serve the Development Team?
1) Coaching the team in self-organization and cross-functionality
2) Helping the team to create high-value products.
3) Removing impediments to their progress.
4) Facilitating Scrum events as needed/requested.
5) Coaching the Team in organizational environments in which Scrum is not yet fully adopted/understood.
63
In which (5) ways does the Scrum Master serve the Organization?
1) Leading and coaching the organization in its Scrum adoption.
2) Planning Scrum implementations.
3) Helping employees and stakeholders understand Scrum empirical product development.
4) Causing change that increases productivity.
5) Working with other Scrum Masters to increase effectiveness of the application of Scrum in the organization.
64
Which are the (5) Scrum events?
1) Sprint,
2) Sprint Planning,
3) Daily Scrum,
4) Sprint Review,
5) Sprint Retrospective
65
What are Scrum events used for?
They are used to create regularity and minimize the need for meetings not defined in Scrum.
66
What time-wise characteristic do Scrum events have?
They're all time-boxed events, such that every event has a maximum duration.
67
Can the duration of a Spring be changed once it starts?
No, once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.
68
In which events can inspection and adaption happen?
Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something.
69
What are Scrum events designed to do?
They are specifically designed to enable critical transparency and inspection.
70
What happens if Scrum events are not included?
It results in reduced transparency and is a lost opportunity to inspect and adapt.
71
What metaphor is used to define the Sprint?
It is the heart of Scrum.
72
How long is a Sprint?
One month or less, it is a time-box.
73
What (3) characteristics must the Product of a Sprint have?
It must be:
* "Done"
* Usable
* Potentially releasable.
74
How is the duration of Sprints when compared to each other?
Consistent throughout a development effort.
75
When does a new Sprint start?
Immediately after the conclusion of the previous Sprint.
76
What are the (5) components of a Sprint?
1) Sprint Planning
2) Daily Scrums
3) Development work
4) Sprint Review
5) Sprint Retrospective
77
What (3) characteristics does a Sprint have?
1) No changes are made that would endanger the Sprint Goal.
2) Quality goals do not decrease
3) Scope may be clarified/re.negotiate between the Product Owner and Developer Team as more is learned.
78
What can a Sprint be considered?
It can be considered a project with no more than a one-month horizon.
79
What is common between a Sprint and a project?
Both are used to accomplish something.
80
What does each Sprint have that is similar to a project?
Each Sprint has a goal of what is to be built, a design and flexible plan what will guide building it, the work and the resultant product increment.
81
What is the maximum length for a Sprint? Why?
One calendar month.
When a Sprint's horizon is too long, the definition of what is being built may change, complexity may rise and risk may increase.
82
How do Sprints enable predictability?
By ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month.
83
How do Sprints limit risk?
Sprints limit risk to one calendar month of cost.
84
Can a Sprint be cancelled before the Sprint time-box is over?
Yes
85
Who has the authority to cancel a Sprint?
Only the Product Owner.
86
Who can influence a Sprint cancellation?
The Stakeholders, the Development Team or the Scrum Master.
87
What happens if the Sprint Goal becomes obsolete?
The Sprint would be cancelled.
88
In which situations does the Sprint Goal become obsolete?
When the company changes direction or if the market or technology conditions change.
89
Why generally cancellation of a Sprint does not make sense?
Because of the short duration of Sprints.
90
What happens with completed and "Done" Product Backlog items when a Sprint is cancelled?
Said items are reviewed and if part of the work is potentially releasable, the Product Owner typically accepts it.
91
What happens with incomplete Product Backlog Items when a Sprint is cancelled?
Said items are re-estimated and put back on the Product Backlog, since the work done on them depreciates quickly and must be frequently re-estimated.
92
Why do Sprint cancellations consume resources?
Because everyone regroups in another Sprint Planning to start another Sprint.
93
How often do Sprint cancellations happen?
They are very uncommon.
94
What happens at Sprint Planning?
The work to be performed in the Sprint.
95
Who plans the Sprint Planning?
The entire Scrum Team.
96
What is the maximum time for a Sprint Planning event?
Eight hours for a one-month Sprint. (For shorter Sprints Sprint Planning is much shorter).
97
What are the (2) responsibilities of a Scrum Master during a Sprint Planning event?
1) Ensures that the event takes place and that attendants understand its purpose.
2) Teaches the Scrum Team to keep it within the time-box.
98
What are the two questions answered during a Sprint Planning?
1) What can be delivered in the Increment resulting from the upcoming Sprint?
2) How will the work needed to deliver the increment be achieved?
99
What does the Development Team do during a Sprint Planning during topic one: What can be done this Sprint?
They work to forecast the functionality that will be developed during the Sprint.
100
What is the mission of the Product Owner during a Sprint Planning during topic one: What can be done this Sprint?
He/she discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal.
101
What is the input to a Sprint Planning meeting? (4)
1) The Product Backlog,
2) the latest product increment,
3) the projected capacity of the Development Team during the Sprint.
4) the past performance of the Development Team,
102
Who decides how many items from the Product Backlog will make the Sprint?
The Development Team. Only they can assess what they can accomplish over the upcoming Sprint.
103
What is crafted during the Sprint Planning by the Scrum Team?
The Sprint Goal
104
What is the Sprint Goal?
It is an objective that will be met withing the Sprint through the implementation of the Product Backlog,
105
What does the Sprint Goal provide?
It provides guidance to the Development Team on why it is building the Increment.
106
What is done once the Sprint Goal is set and the Product Items from the backlog have been selected for the Sprint?
Topic Two: "How will the chosen work get done?" is addressed.
107
What is the main goal of the Development Team during Topic Two: How will the chosen work get done?
The dev. Team decides how it will build the functionalities they will work on into a "Done" product Increment during the Spint.
108
What is the name received by the Product Backlog items selected for a Sprint and their delivery plan?
The Sprint Backlog
