Scrum events Flashcards
Why events are used in Scrum?
to create regularity and to minimize the need for meetings
The sprint timebox
One month or less
When a new sprint starts
A new Sprint starts immediately after the conclusion of the previous Sprint.
What can happen during the sprint
Scope may be clarified and renegotiated with the Product Owner as more is learned.
The Product Backlog is refined as needed; and,
No changes are made that would endanger the Sprint Goal;
Problems with a sprint too long
Sprint Goal may become invalid,
complexity may rise,
and risk may increase
Benefits of shorter sprints
generate more learning cycles
limit risk of cost and effort to a smaller time frame
When a sprint can be cancelled
When the sprint goal becomes obsolete
Who can cancel the sprint
Product owner
Sprint planning timebox
8 hours for one month
Who goes to the sprint planning
The scrum team,
Stakeholders to provide advice
Three topics of sprint planning
Why is this Sprint valuable?
What can be Done this Sprint?
How will the chosen work get done?
What is the Sprint backlog?
Sprint Goal,
the Product Backlog items selected for the Sprint,
plus the plan for delivering them
Topic One: Why is this Sprint valuable?
The Product Owner proposes how the product could increase its value and utility in the current Sprint
The Scrum Team together defines a Sprint Goal
Topic Two: What can be Done this Sprint?
the Developers select items from the Product Backlog to include in the current Sprint, with help from the PO
Topic Three: How will the chosen work get done?
For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done.
Who can define how PB items are turned into increments?
Only the developers
Daily Scrum timebox
15-minutes or less
Daily Scrum purpose
to inspect progress toward the Sprint Goal
adapt the Sprint Backlog as necessary,
Who is neeed in the daily scrum
Only the Devs
If the PO or SM are working on the PB items, they participate as devs
Daily scrum - how it reduces complexity
Held same time and place every day
Why the Daily is important
improve communications,
identify impediments,
promote quick decision-making,
eliminate the need for other meetings.
Sprint Review timebox
4 hours or less
Sprint review purpose
Inspect the outcome of the Sprint and determine future adaptations
Sprint review goal
Devs to review what was accomplished
Adjust PB to meet new opportunities
Sprint Review, place in the sprint
Second to last event
Sprint Retrospective purpose
plan ways to increase quality and effectiveness.
Elements inspected in the retrospective
interactions,
processes,
tools,
Definition of Done
Discussion of the Retroespective
what went well during the Sprint,
what problems it encountered,
and how those problems were (or were not) solved.
Sprint retrospective outcomes
The Scrum Team identifies the most helpful changes to improve its effectiveness.
The most impactful improvements are addressed as soon as possible
Sprint retrospective, place in the sprint
Last event
Finishes the sprint
