Follow

Sprints

In the Scrum methodology of agile software development, work is confined to a regular, repeatable work cycle, known as a sprint. Another definition of a sprint is that it is a time-boxed iteration. The length of each sprint will differ between environments but is usually between 1 week (recommended) and 3 months.

During each sprint the team develops a certain set of work items. Every sprint begins with the sprint planning meeting, in which the Product Owner and the team discuss which work items will be moved from the product backlog into the sprint backlog.

The Sprint Goal, aka Sprint Theme, is the key focus of the work for a single sprint. A sprint also forms part of the further discussions during the Sprint Review and Sprint Retrospective meetings.

During the sprint, team members check in with each other at the daily Scrum meeting. After sprint execution, a sprint review meeting is conducted. The team also gathers at the end of each sprint to reflect on how things went and what they’d like to change. This meeting is called the sprint retrospective meeting.

Sprints are created per team – if there are multiple teams there can therefore be multiple sprints in progress at the same time.

Next, let’s look at the Sprint Planning and Sprint Review categories:

Sprint_Planning.jpg

Category: Sprint Planning

1.1.1        Project – All sprints need to be captured under the “Development” project.
1.1.2        Status – The status of the sprint is selected, and will also show on the “Scrum - Sprint Backlog” dashboard. There are three statuses that can be selected for each sprint. They are Planned, In Progress and Deployed.
1.1.3        Start– This shows the start date of the weekly sprint.
1.1.4        End – This is a calculated field indicating the last day of the sprint. By default, this is set for a one week sprint. The sprints are run from the Sunday to the Saturday.
1.1.5        Goal – The goal for the sprint is captured and shows on the “Scrum - Sprint Backlog”. The goal also reflects on the “Scrum – Sprint Backlog”.
1.1.6        Estimated Hours – This is a calculated field that will show the total estimated hours for all work items linked to the sprint.
1.1.7        Estimate to Complete – This is a calculated field which shows the total estimate to complete hours, for the work items linked to the sprint.
1.1.8        Team – The team responsible for the sprint will be displayed here. This indicates that there can only be one team per sprint.
1.1.9        Link to Sprint Dashboard – This is a hyperlink to the “Scrum - Sprint Backlog” for the specific sprint you are viewing.

Sprint_Review.jpg

Category: Sprint Review

1.1.10        What went well? – During the Sprint Retrospective meeting this field is populated with the relevant information.
1.1.11        What went wrong – During the Sprint Retrospective meeting this field is populated with the relevant information.
1.1.12        Velocity – This is a calculated field that will show the total estimated hours for all work items linked to the sprint AND that have been completed, excluding generic work items.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request
Article is closed for comments.
Start a 30 Day Free TrialClick ClickNo Credit Card and No Obligation
Powered by Zendesk