Scrum defines four events (sometimes called ceremonies) that occur inside each sprint: sprint planning, daily scrum, sprint review, and sprint retrospective.
Please note, the following information comes from the thought leadership of our Certified Scrum Trainers and Certified Agile Coaches, as well as other reputable sources, including the Agile Manifesto and the November 2017 version of the Scrum Guide.
What Happens in Sprint Planning?
During sprint planning, the entire Scrum team collaborates and discusses the desired high-priority work for the sprint and defines the sprint goal. The Scrum Master’s role is primarily to facilitate the meeting. The Product Owner describes the objective of the sprint and also answers questions from the development team about execution and acceptance criteria/criteria of satisfaction. The development team has the final say in how much of the high-priority work it can accomplish during the sprint.
Who attends Sprint Planning?
Sprint planning involves the entire Scrum team: the development team, Product Owner, and Scrum Master.
How long should Sprint Planning Last?
Sprint planning is limited to a maximum of eight hours.
The general rule of thumb is to allow two hours of sprint planning for every one week of sprint length. That means teams should timebox sprint planning to four hours for a two-week sprint and eight hours for a one-month sprint.
What Happens in a Daily Scrum?
The development team meets for 15 minutes (or less) every day of the sprint to inspect progress toward the sprint goal. They describe for each other how their own work is going, ask for help when needed, and consider whether they are still on track to meet the sprint goal. This is not a status meeting but is instead an opportunity for the development team to inspect and adapt the product and process on a daily basis.
Who Attends the Daily Scrum?
The mandatory participants at the daily scrum are the development team. The Scrum Master typically attends but is optional. The Product Owner is invited but doesn’t have to attend.
What Happens in a Sprint Review?
Sprint reviews focus on the product being developed, specifically on the potentially shippable product increment created during the sprint. During a sprint review, the Scrum team invites stakeholders to discuss what was completed during the sprint. They adapt the product backlog as needed based on this feedback. The Product Owner has the option to release any of the completed functionality.
Though a demo might be part of this meeting, the primary purpose of the sprint review is the inspect and adapt capability provided by the discussion.
Who Attends a Sprint Review?
The entire Scrum team attends the sprint review. Any stakeholders, senior managers, and other affected departments (e.g., marketing, customer support) are invited to attend and give feedback. Scrum teams should invite as many people as the room can hold--diverse feedback is essential for creating excellent products.
How Long Should Sprint Reviews Last?
Sprint reviews are limited to a maximum of four hours.
The general rule of thumb is to allow one hour for sprint review every one week of sprint length. That means teams should timebox sprint review to two hours for a two-week sprint and four hours for a one-month sprint.
What Happens in a Sprint Retrospective?
Sprint retrospectives focus on the process. During a sprint retrospective, the Scrum team discusses what went right and areas for improvement in the sprint. They make tangible plans for how to improve their own process, tools and relationships.
What Is the Difference between Sprint Reviews & Sprint Retrospectives?
Sprint reviews focus on the product. Sprint retrospectives focus on the process.
Who Should Attend a Sprint Retrospective?
Sprint retrospectives are for the Scrum team, which would include the development team, Scrum Master, and Product Owner. In practice, product owners are recommended but not mandatory attendees.
How Long Should Sprint Retrospectives Last?
Sprint retrospectives are limited to a maximum of three hours.
The general guidance is to allow 45 minutes for each week of sprint length. So a two-week sprint would cap the sprint retrospective at an hour and a half; a four-week sprint at three hours.
Transitioning to an agile framework such as Scrum requires a new mindset and overall cultural adjustments. And like all change, it doesn't come easy. But when teams and organizations fully commit to Scrum, they'll discover a new sense of flexibility, creativity, and inspiration - all of which will lead to greater results.
Ready to get a Scrum certification?