Understanding and Applying the Scrum Framework · Topic 4 of 5
Sprint Review, Daily Scrum and Sprint Retrospective
The Sprint Review, Daily Scrum and Sprint Retrospective for PSPO I: timeboxes, who takes part, and the Product Owner's role in each event.
- 4 min
- Sprint Review: up to 4 hours for a one-month Sprint; outcome inspected with key stakeholders; Product Backlog may be adjusted.
- The Sprint Review is a working session, not a demo or a sign off.
- Daily Scrum: 15 minutes, for the Developers; the Product Owner joins as a Developer only when working on Sprint Backlog items.
What it is
Besides Sprint Planning, three events happen in each Sprint. The Daily Scrum inspects progress toward the Sprint Goal every day. The Sprint Review inspects the outcome of the Sprint with key stakeholders and decides future adaptations. The Sprint Retrospective plans ways to increase quality and effectiveness and concludes the Sprint.
The Sprint Review matters most to a Product Owner: it is where the product meets its stakeholders and where the Product Backlog is adjusted.
How it works
Timeboxes
| Event | Maximum timebox for a one-month Sprint |
|---|---|
| Sprint | One month |
| Sprint Planning | 8 hours |
| Daily Scrum | 15 minutes, whatever the Sprint length |
| Sprint Review | 4 hours |
| Sprint Retrospective | 3 hours |
For shorter Sprints, events are usually shorter. Timeboxes are maximums.
Sprint Review
- Purpose: to inspect the outcome of the Sprint and determine future adaptations.
- The Scrum Team presents the results of its work to key stakeholders, and progress toward the Product Goal is discussed.
- The Scrum Team and stakeholders review what was accomplished and what has changed in their environment. Based on this, attendees collaborate on what to do next.
- The Product Backlog may be adjusted to meet new opportunities.
- It is a working session; the Scrum Team should avoid limiting it to a presentation.
- It is the second to last event of the Sprint.
Only work that meets the Definition of Done is part of an Increment. Items that are not Done cannot be presented at the Sprint Review.
| Product Owner at the Sprint Review | Not the Product Owner's job |
|---|---|
| Discuss progress toward the Product Goal | Grade the Developers' performance |
| Collaborate with stakeholders on what to do next | Hold a formal sign off before anything can be released |
| Adjust the Product Backlog to new opportunities | Present undone work to keep stakeholders happy |
Daily Scrum
- Purpose: to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.
- It is an event for the Developers, held at the same time and place every working day.
- If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.
- The Developers choose the structure and techniques, as long as it produces an actionable plan for the next day of work.
A Product Owner who is not working on Sprint Backlog items does not need to attend. The Daily Scrum is not a status report to the Product Owner.
Sprint Retrospective
- Purpose: to plan ways to increase quality and effectiveness.
- The Scrum Team, including the Product Owner, inspects how the last Sprint went with regard to individuals, interactions, processes, tools and the Definition of Done.
- The most impactful improvements are addressed as soon as possible and may even be added to the Sprint Backlog for the next Sprint.
- It concludes the Sprint.
The Product Owner is a member of the Scrum Team, so the Product Owner takes part in the Sprint Retrospective. Options that leave the Product Owner out are wrong.
How the exam asks about this
- "What is the purpose of the Sprint Review?" To inspect the outcome of the Sprint and determine future adaptations.
- "Must the Product Owner attend the Daily Scrum?" Only if actively working on Sprint Backlog items, then as a Developer.
- "Does the Product Owner attend the Sprint Retrospective?" Yes, as a member of the Scrum Team.
- "Can an Increment be released before the Sprint Review?" Yes; the Sprint Review is not a gate to releasing value.
What to remember for the exam
- Sprint Review: up to 4 hours for a one-month Sprint; outcome inspected with key stakeholders; Product Backlog may be adjusted.
- The Sprint Review is a working session, not a demo or a sign off.
- Daily Scrum: 15 minutes, for the Developers; the Product Owner joins as a Developer only when working on Sprint Backlog items.
- Sprint Retrospective: up to 3 hours; the whole Scrum Team; concludes the Sprint.
- Work that is not Done is not shown at the Sprint Review.
The Sprint Review should never be considered a gate to releasing value. Increments may be delivered to stakeholders before the end of the Sprint.
Common mistakes
Turning the Sprint Review into a slide demo. It is a working session with stakeholders.
Using the Daily Scrum to report to the Product Owner. It is a planning event for the Developers.
Leaving the Product Owner out of the Retrospective. The Product Owner is part of the Scrum Team.
Check yourself
What may happen to the Product Backlog at the Sprint Review?
It may be adjusted to meet new opportunities.
When does the Product Owner take part in the Daily Scrum?
When actively working on items in the Sprint Backlog, as a Developer.
Which event concludes the Sprint?
The Sprint Retrospective.
Topic 4 of 5 in Understanding and Applying the Scrum Framework
Test yourself on Understanding and Applying the Scrum Framework
The full Scrum.org PSPO I question bank has 1,065 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Scrum.org. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.