Understanding and Applying the Scrum Framework · Topic 4 of 5
Daily Scrum, Sprint Review and Sprint Retrospective
The Daily Scrum, Sprint Review and Sprint Retrospective for PSM I: purpose, who takes part, timeboxes and what each event inspects and adapts.
- 4 min
- Includes a diagram
- Daily Scrum: 15 minutes, for the Developers, same time and place, produces an actionable plan for the next day.
- Sprint Review: up to 4 hours for a one-month Sprint, inspects the outcome with key stakeholders.
- Sprint Retrospective: up to 3 hours for a one-month Sprint, inspects individuals, interactions, processes, tools and the Definition of Done.
What it is
Besides Sprint Planning, three events happen within each Sprint. The Daily Scrum inspects progress toward the Sprint Goal every day. The Sprint Review inspects the outcome of the Sprint with stakeholders. The Sprint Retrospective plans ways to increase quality and effectiveness, and concludes the Sprint.
How it works
Timeboxes
| Event | Maximum timebox for a one-month Sprint |
|---|---|
| Sprint | One month |
| Sprint Planning | 8 hours |
| Daily Scrum | 15 minutes, for any Sprint length |
| Sprint Review | 4 hours |
| Sprint Retrospective | 3 hours |
For shorter Sprints, the events are usually shorter. Timeboxes are maximums: an event can end early once its purpose is achieved.
Daily Scrum
- Purpose: to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
- Who: an event for the Developers. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.
- Held at the same time and place every working day of the Sprint to reduce complexity.
- The Developers can select whatever structure and techniques they want, as long as it focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.
- It is not the only time Developers can adjust their plan; they often meet throughout the day.
Sprint Review
- Purpose: to inspect the outcome of the Sprint and determine future adaptations.
- The Scrum Team presents the results of their work to key stakeholders, and progress toward the Product Goal is discussed.
- Attendees collaborate on what to do next; the Product Backlog may also 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.
Sprint Retrospective
- Purpose: to plan ways to increase quality and effectiveness.
- The Scrum Team inspects how the last Sprint went with regard to individuals, interactions, processes, tools and their Definition of Done.
- It identifies the most helpful changes; 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 Daily Scrum belongs to the Developers. The Scrum Master ensures it takes place, but does not need to run it, and it is not a status report to the Product Owner or Scrum Master.
How the exam asks about this
- "What is the purpose of the Daily Scrum?" To inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
- "Should the Sprint Review be a slide presentation?" No, it is a working session.
- "Which event concludes the Sprint?" The Sprint Retrospective.
What to remember for the exam
- Daily Scrum: 15 minutes, for the Developers, same time and place, produces an actionable plan for the next day.
- Sprint Review: up to 4 hours for a one-month Sprint, inspects the outcome with key stakeholders.
- Sprint Retrospective: up to 3 hours for a one-month Sprint, inspects individuals, interactions, processes, tools and the Definition of Done.
- The Retrospective concludes the Sprint.
- Timeboxes are maximums; events can end early.
The Sprint Review is not a gate for releasing value. Increments can be delivered to stakeholders before the end of the Sprint.
Common mistakes
Turning the Daily Scrum into a status meeting. It is for the Developers to plan.
Inviting stakeholders to decide acceptance in the Review. It is a working session to inspect and adapt.
Skipping the Retrospective when things went well. It is part of every Sprint; skipping it loses an opportunity to inspect and adapt.
Check yourself
What is the maximum timebox of the Sprint Retrospective for a one-month Sprint?
Three hours.
Who is the Daily Scrum for?
The Developers.
What does the Sprint Retrospective inspect?
How the last Sprint went with regard to individuals, interactions, processes, tools and the Definition of Done.
Topic 4 of 5 in Understanding and Applying the Scrum Framework
Test yourself on Understanding and Applying the Scrum Framework
The full Scrum.org PSM I question bank has 811 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.