Scrum Events Flashcards
Are the heartbeat of Scrum,
Sprint
The Scrum Team turns a selection of the work
into an Increment of value during a…
Sprint
Are fixed length events of one month or less
to create consistency
Sprint
a container for all other events -
All the work necessary to achieve the Product
Goal, including Sprint Planning, Daily Scrums,
Sprint Review, and Sprint Retrospective,
happen within…
Sprint
A new Sprint starts immediately after the
conclusion of the previous Sprint.
Sprint
All the work necessary to achieve the Product
Goal, including Sprint Planning, Daily Scrums,
Sprint Review, and Sprint Retrospective,
happen within…
Sprint
enable predictability by ensuring
inspection and adaptation of progress toward
a Product Goal at least every calendar month
Sprint
Each “…” may be considered a short project
Sprint
could be cancelled if the Sprint Goal
becomes obsolete
Sprint
Only the Product Owner has the authority to
cancel the…
Sprint
Working in “…” at a sustainable pace
improves the Scrum Team’s focus and
consistency
Sprint
No changes are made that would endanger
the Sprint Goal
Sprint
Quality does not decrease
Sprint
Product Backlog is refined as needed
Sprint
The Sprint Goal is the single objective for the “…”
Sprint
Scope may be clarified and renegotiated with
the Product Owner as more is learned
Sprint
As more is learned during the “…”, plans
created initially are updated frequently and at
least once every day
Sprint
Multiple Increments may be created within a “…”
Sprint
Working in “…” at a sustainable pace
improves the Scrum Team’s focus and
consistency
Sprint
is timeboxed to a maximum of eight hours for a one-month Sprint.
For shorter Sprints, the event is usually shorter
sprint planning
The Product Owner ensures that attendees are prepared to discuss
the most important Product Backlog items and how they map to the
Product Goal
sprint planning
The Scrum Team may also invite other people to attend “…” to provide advice
sprint planning
Product Backlog items that can be Done by the Scrum Team within
one Sprint are deemed ready for selection in a “…”
sprint planning
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 whole Scrum Team then collaborates to define a Sprint Goal
that communicates why the Sprint is valuable to stakeholders. - The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog
- The Sprint Goal must be finalized prior to the end of Sprint Planning.
Topic Two: What can be Done this Sprint?
- 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, which
increases understanding and confidence. - The more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts
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 - This is often done by decomposing Product Backlog items into
smaller work items of one day or less (common practice is to create
various “tasks” for the work involved to turn the PBI to an Increment) - How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value
The purpose is to inspect progress
toward the Sprint Goal and adapt the
Sprint Backlog as necessary,
adjusting the upcoming planned work
daily scrum
To reduce complexity, it is held at the
same time and place every working
day of the Sprint.
daily scrum
Is a 15-minute event for the
Developers
daily scrum
If the Product Owner or Scrum Master
are actively working on items in the
Sprint Backlog, they participate as
Developers
daily scrum
The Developers can select whatever
structure and techniques they want,
as long as this event focuses
on progress toward the Sprint Goal
and produces an actionable plan for
the next day of work
daily scrum
This event improves communications,
identify impediments, promote quick
decision-making, and consequently
eliminate the need for other meetings
daily scrum
The Daily Scrum is not the only time
Developers are allowed to adjust their
(Sprint) plan.
They often meet throughout the day
for more detailed discussions about
adapting or re-planning the rest of the
Sprint’s work
The Sprint Backlog] should have
enough detail that they can inspect
their progress in the…
daily scrum
Not part of Scrum (as of Nov 2020),
but complimentary practice -
Developers answer 3 questions with
respect to the Sprint Goal
– (a) what
did I do yesterday to help the team
achieve the Sprint Goal (b) what am I
looking to do today to help the team
achieve the Sprint Goal (c) what
impediments do I have that is slowing
me/others in achieving Sprint Goal?
purpose of this meeting is to
inspect the outcome of the Sprint and
determine future adaptations.
sprint review
It is the second to last event of the
Sprint
sprint review
It is timeboxed to a maximum of four
hours for a one-month Sprint. For
shorter Sprints, the event is usually
shorter
sprint review
the sum of the Increments is
presented at the “…” thus
supporting empiricism
sprint review
The Scrum Team presents the results
of their work to key stakeholders and
progress toward the Product Goal is
discussed
sprint review
The Scrum Team and stakeholders
review what was accomplished in the
Sprint and what has changed in their
environment
sprint review
Based on this information, attendees
collaborate on what to do next
sprint review
PO’s decisions are visible in the
content and ordering of the Product
Backlog, and through the inspectable
Increment at the “…’”
sprint review
The Product Backlog may also be
adjusted (adapted) to meet new
opportunities
sprint review
It is a working session and the Scrum
Team should avoid limiting it to a
presentation
sprint review
should never be considered a gate to releasing value.
sprint review
If a Product Backlog item does not
meet the Definition of Done, it cannot
be released or even presented at the “…”
sprint review
The purpose is to plan ways
to increase quality and
effectiveness
sprint retrospective
This event concludes the
Sprint
sprint retrospective
sprint retrospectiveThe Scrum Team inspects how
the last Sprint went with
regards to individuals,
interactions, processes, tools,
and their Definition of Done
sprint retrospective
Inspected elements often also
vary with the domain of work
sprint retrospective
Also, assumptions that led the
Scrum Team astray are
identified and their origins
explored
sprint retrospective
The Scrum Team discusses
what went well during the
Sprint, what problems it
encountered, and how those
problems were (or were not)
solved
sprint retrospective
The Scrum Team identifies the
most helpful changes to
improve its effectiveness
sprint retrospective
The most impactful
improvements are addressed
as soon as possible. They may
even be added to the Sprint
Backlog for the next Sprint
sprint retrospective
