Introduction to The Sprint

Unlike the other Scrum Events, the Sprint isn’t a meeting. Instead, it’s the container for all of the work that’s done by a Scrum Team to achieve a Sprint Goal. The Daily Scrum, Sprint Planning, Sprint Review and Sprint Retrospective all fall within the Sprint as well as Product Backlog Refinement.

There is no work done in Scrum that is outside the Sprint and there are no gaps between Sprints. When one ends, the next one immediately begins. Each Sprint starts with a planning meeting (Sprint Planning) and ends with a review of the work completed during the Sprint (Sprint Review) and a review of how the Sprint went (Sprint Retrospective). During the Sprint, the Developers meet daily (Daily Scrum) to review their progress toward their Sprint Goal. 

Sprints should be no longer than one month in duration to support the Scrum tenet of rapid feedback loops.

The Sprint

 

 

Resources:

Module
The Sprint Goal is a “commitment” for the Sprint Backlog meaning that it is meant to provide focus for the Scrum Team and a target against which progress can be measured. The Sprint Goal provides the objective for the Sprint and frames many of the events during the Sprint:Objective: The Sprint Goal ...
4.8 from 14 ratings
Learning Series
The Sprint Backlog represents what the Developers plan to accomplish during the Sprint. Learn about the Sprint Backlog, Sprint Goal, how to use Sprint Backlogs effectively and investigate common antipatterns with the Sprint Backlog.

 

Learning Series
Every Sprint starts with Sprint Planning where the Scrum Team determines what they plan to accomplish during the course of the Sprint. They make this transparent by creating a Sprint Backlog including the Sprint Goal, the selected Product Backlog Items and the Developers’ plan for delivering the work
Learning Series
To keep work moving smoothly, the Developers get together for 15 minutes every day to focus on the Sprint Goal and to plan the upcoming day’s work. During the Daily Scrum, they identify any issues they need help in resolving, ask for help when they need it and adjust the Sprint Backlog, if necessary.

 

Learning Series
The Sprint Review is a working meeting where the Scrum Team presents their completed work to stakeholders and asks for feedback. The Scrum Team and stakeholders discuss the progress made toward the Product Goal, emerging changes in the business or technical climate and collaborate on what to do next
Learning Series
The Sprint Retrospective is the last event in the Sprint. Unlike other Scrum Events where the focus is on inspecting and adapting ways to improve the product, the Sprint Retrospective is a place for the Scrum Team to inspect and adapt their working practices.

 

Video
In this video you will get some helpful tips for facilitating a Product Backlog refinement session. (4:41 Minutes)
4.4 from 91 ratings
 

What did you think about this content?

Included In

Learning Series
Unlike the other Scrum Events, the Sprint isn’t a meeting. Instead, it’s the container for all of the work that’s done by a Scrum Team to achieve a Sprint Goal. The Daily Scrum, Sprint Planning, Sprint Review and Sprint Retrospective all fall within the Sprint.