Each one serves a distinct purpose and is designed to bring a specific set of participants together in a scheduled sequence to ensure a successful project outcome.
I. Sprint Planning
Sprint Planning is the first event in any Scrum Sprint and takes place before work begins. The main purpose is to determine what the team should work on during the forthcoming Sprint and to create a viable plan for this work.
The participants generally include the Product Owner, the Scrum Master, and the Development Team. It’s critical to have each of these roles involved to ensure the team has a clear understanding of the project objectives and their role in accomplishing them.
In terms of sequence, Sprint Planning follows the order below:
- Review the Product Backlog – Items are reviewed in priority order, with the highest-priority items discussed first.
- Team Selection – The Development Team selects the items they believe they can deliver by the end of the Sprint.
- Sprint Goal – The Product Owner sets the Sprint goal which serves as a summary objective for the Sprint.
The maximum timebox for Sprint Planning is 2 hours per week of a Sprint, which means for a four-week Sprint, the Sprint Planning should not exceed 8 hours.
II. Daily Scrum
The Daily Scrum is a short, daily event where the Development Team synthesizes progress on the Sprint Goal. The major purpose here is to inspect the work completed since the previous Daily Scrum and plan the work for the next 24 hours.
The core participants are the Development Team members. Though, the Scrum Master and Product Owner may attend, but only as observers.
The sequence follows three main questions:
- What did I do yesterday to help the team achieve the Sprint Goal?
- What will I do today to help the team achieve the Sprint Goal?
- Are there any obstacles in my way?
The maximum timeboxed duration for the Daily Scrum is 15 minutes, regardless of the Sprint length.
III. Sprint Review
The Sprint Review takes place at the end of the Sprint and serves to inspect the Increment and adapt the Product Backlog.
Participants include the Scrum Team and key stakeholders invited by the Product Owner, ensuring transparency and alignment across the board.
The sequence of a Sprint Review includes:
- The Product Owner presents which Product Backlog items are “Done”.
- The Development Team presents the work done and answers questions.
- The Product Owner presents the likely target completion dates.
- The entire group collaborates on the next steps.
The maximum timeboxed duration for a Sprint Review is 1 hour per week of Sprint duration.
IV. Sprint Retrospective
The Sprint Retrospective happens after the Sprint Review and prior to the next Sprint Planning. The Retrospective serves to inspect the last Sprint and to plan ways to increase quality and effectiveness.
The participants at a Sprint Retrospective include the Scrum Team.
The sequence includes:
- All team members reflect on the past Sprint.
- Team members discuss what went right and where there’s room for improvements.
- They then create a plan for improvements to be implemented during the next Sprint.
The maximum timebox for the Sprint Retrospective is 1.5 hours per week of Sprint duration.
Event | Purpose | Participants | Sequence | Timebox |
---|---|---|---|---|
Sprint Planning | Plan the Sprint | Scrum Team | Product Backlog Review, Team Selection, Sprint Goal | 2 hours per week of Sprint |
Daily Scrum | Daily planning | Development Team | Daily Progress, Plan for next day, Obstacles | 15 minutes |
Sprint Review | Inspect Increment and adapt the Product Backlog | Scrum Team and stakeholders | Presentation of Backlog items and work done, Next steps | 1 hour per week of Sprint |
Sprint Retrospective | Reflect on the Sprint and plan for improvements | Scrum Team | Reflection, Discussion, Improvement Plan | 1.5 hours per week of Sprint |
Scrum is a flexible and adaptable framework that depends on regular feedback and continuous improvement. Understanding these events and their purpose, participants, sequences, and timing is fundamental in successfully implementing and making the best use of the Scrum framework.
Practice Test
True or False: Sprint Planning is a process that includes all team members, including the Product Owner and the Scrum Master.
- True
- False
Answer: True
Explanation: In Sprint Planning, all Scrum team members, including the Product Owner and the Scrum Master, have a role as they collaborate on understanding the work of the Sprint.
True or False: The Sprint Review is conducted at the end of the Sprint to inspect the outcome and decide on the next steps.
- True
- False
Answer: True
Explanation: The Sprint Review is a meeting held at the end of the Sprint to inspect what was done during the Sprint and to adapt the Product Backlog if necessary.
In the Daily Scrum, who is responsible for updating the burndown chart?
- A. Scrum Master
- B. Product Owner
- C. The Development Team
Answer: C. The Development Team
Explanation: During the Daily Scrum, the Development Team is responsible for tracking and communicating their progress, which includes updating the burndown chart.
The maximum recommended timebox for the Sprint Retrospective for a one-month Sprint is:
- A. 1 hour
- B. 2 hours
- C. 3 hours
Answer: C. 3 hours
Explanation: According to the Scrum guide, for a one-month Sprint, the Sprint Retrospective should not exceed three hours.
Multiple Select: The main participants in the Sprint Review are:
- A. Scrum Master
- B. Development Team
- C. Stakeholders
- D. Product Owner
Answer: A, B, C, D
Explanation: All option are right as Scrum Master, Development Team, Stakeholders and Product Owner are the main participants in the Sprint Review.
True or False: The purpose of the Daily Scrum is to discuss in detail the work performed the previous day.
- True
- False
Answer: False
Explanation: The purpose of the Daily Scrum is to inspect the progress towards the Sprint Goal and adapt the plan for the next 24 hours, not to discuss work in detail.
The sequence of Scrum events is:
- A. Sprint Planning -> Daily Scrum -> Sprint Review -> Sprint Retrospective
- B. Sprint Review -> Sprint Planning -> Daily Scrum -> Sprint Retrospective
- C. Sprint Planning -> Sprint Review -> Daily Scrum -> Sprint Retrospective
Answer: A. Sprint Planning -> Daily Scrum -> Sprint Review -> Sprint Retrospective
Explanation: The sequence of the Scrum events starts with Sprint Planning, followed by Daily Scrum meetings, the Sprint Review, and finally the Sprint Retrospective.
How many hours is the maximum recommended timebox for the Sprint Planning?
- A. 4 hours
- B. 8 hours
- C. 2 hours
Answer: B. 8 hours
Explanation: For a one-month Sprint duration, the maximum recommended timebox for the Sprint Planning is 8 hours.
True or False: The purpose of the Sprint Retrospective is to plan for the next Sprint.
- True
- False
Answer: False
Explanation: The purpose of the Sprint Retrospective is to inspect and adapt the Sprint and identify improvements for the next Sprint.
True or False: The Sprint Review contains the functionality of the Product Backlog Items done in the Sprint that is likely to be included in the next release.
- True
- False
Answer: True
Explanation: During the Sprint Review, the Scrum Team and stakeholders assess what was accomplished in the Sprint and what has changed in their environment, considering what is now the most valuable thing to do next.
Interview Questions
What is the purpose of Sprint Planning in Scrum?
Sprint Planning is a timeboxed working session that lasts roughly 1 hour for every week of the sprint. In sprint planning, the entire team agrees on a set of goals for the upcoming Sprint and develops a Sprint Backlog that, if delivered, will reach the Sprint Goal.
Who are the participants in the Daily Scrum?
The participants in the Daily Scrum are typically the Scrum Team (the Product Owner, Scrum Master, and Development Team)
What is the sequence of activities in Sprint Review?
In a Sprint Review, first, the Product Owner identifies what has been done and what hasn’t been done. The Development team discusses what went well during the sprint and demonstrates the work that it has “done”. The team then discusses what problems it ran into and those it resolved. The Product Owner discusses the Product Backlog and may project likely target and delivery dates.
What is the maximum recommended timebox for a Sprint Retrospective?
The maximum recommended timebox for a Sprint Retrospective is three hours for a one-month Sprint. For shorter Sprints, it is usually shorter.
What is the purpose of the Daily Scrum?
The purpose of the Daily Scrum is to inspect progress towards the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
Who should attend the Sprint Review?
The Sprint Review should be attended by the Scrum Team and key stakeholders invited by the Product Owner.
Why is Sprint Planning important?
Sprint Planning sets the direction and tone for the entire sprint. It provides the team with clear focus and guidance on what needs to be achieved, who is doing what, and what the expectations are.
Who leads the Daily Scrum?
The Daily Scrum is facilitated by the Development Team. However, the Scrum Master ensures that the meeting takes place and that attendants understand its purpose.
What happens in a Sprint Retrospective?
In a Sprint Retrospective, the team reflects on the past sprint to identify and agree on continuous process improvement actions.
How long should the Sprint Planning last?
Sprint Planning should last no more than 8 hours for a one-month Sprint. For shorter sprints, it usually shorter.