Continuing with the Scrum FAQ series, in today's post we'll talk about Sprints. We will see what a Sprint is, as it is created and what things should look like before, during and after a sprint.
Scrum in the development process is divided in regular cycles. Sprints are each of these cycles. According to the definition we can find in the post "Learning the Scrum terms – Glossary", we learned that Sprint "represents a duty cycle in Scrum. This cycle can be 2, 3 or 4 weeks. Sprints should always have the same duration. "On every Sprint, a set of requirements is implemented, resulting in an increase in the product being developed.”
The diagram below represents the cycle of a Sprint.
Before starting a Sprint – Planning
Before starting the sprint, you need to make Stories for the Product Backlog, to be implemented in the cycle that is about to start. The stories in the Product Backlog should be in a priority order defined by the PO and must be estimated by the development team.
Once the Product Backlog is prioritized and estimated the development team held a planning meeting (Planning 1) to select the stories that will be included in the specific Sprint in order to accommodate them within the timeframe of the Sprint and respecting the prioritization defined PO. This set of stories included in the Sprint is called Sprint Backlog.
Once the Sprint Backlog is defined, the Sprint can then be started! At this point the development team should have a planning meeting (Planning 2), in which each story is split up into smaller tasks in order to have greater control over the development of each story individually.
Now it's down to work! We have the stories to be implemented and the tasks to be undertaken to implement each story.
Implementation of a Sprint
During a Sprint, the team performs tasks for the realization of the stories in the order of priority set by the PO. During the Sprint the team can use the Burndown chart to find out if the Sprint is delayed or ahead of the Sprint's goal and take action if necessary.
Every day the development team meets to talk about what was done yesterday, what are the impediments and what will be done in the present day. If there are impediments, the Scrum Master seeks to resolve it as quickly as possible so that staff can proceed with working on the Sprint.
The Scrum Master is also part of daily meeting, if possible. It is recommended that there be no change in the time of the tasks in the Sprint or Sprint Backlog.
After a Sprint – Review Meeting and Retrospective Reunion
At the end of the Sprint, the Sprint Review meeting is held. In this meeting, the team presents the stories in the Sprint that were implemented, showing the result to the PO. The PO then analyzes the resolution of each story with the development team and decides whether to approve each one or not.
The stories that are not approved are than returned to the Product Backlog and are available for inclusion in a new Sprint. At this meeting, taking advantage that the PO and the team are together, stories from the product backlog that have not been well understood by the development team may also be discussed.
After the review meeting, the development team and the Scrum Master have the Retrospective Meeting.
In this meeting, the team shares their views and reflects on what did and did not work during the Sprint. A discussion is made about the strengths and weaknesses of the Sprint, with the aim to reinforce what was good and finding solutions to what was bad. So in every Sprint, the team will learn and improve your development process.