Sprints & Sprint Planning

A sprint is a fixed period — usually one to four weeks — that a team fills with tickets and then works through. This article covers creating a sprint, filling it, starting it, and completing it.

Sprint Planning

Open a project and select the Sprints tab. The page is titled Sprint Planning and lists the project's sprints with their Status, Points and Remaining.

A sprint is in one of three states:

• Planning — being filled, not started
• Active — running. One sprint at a time.
• Completed — finished

Create a sprint

1. Select Create Sprint.
2. Enter the Name.
3. Set the Start Date and End Date. Both are required.
4. Write a Goal — one sentence on what this sprint is for.
5. Select Create Sprint.

The new sprint appears in the list with status Planning.

Fill the sprint

Go to the project's Backlog tab. Select Groom to estimate anything without points, then tick the tickets you want and use the sprint picker that appears to move them across.

Selecting the sprint back on Sprint Planning shows its committed points and hours, so you can tell whether the team has taken on more than it usually finishes. The Velocity tile in the sprint's metrics gives you that comparison. There is no separate capacity field to fill in — the totals come from the tickets themselves.

Start the sprint

1. Select the sprint in the list.
2. Select Start Sprint. The button appears only while the sprint is in Planning.

The sprint's status changes to Active. The board's sprint selector now offers it, so the team can filter down to just this sprint's work.

Track the sprint

The selected sprint shows four metrics: Velocity, Burn Rate in points per day, Total Tickets and Completed. Its Sprint Goal sits alongside them and can be edited mid-sprint with Edit Goal.

For the burndown chart, use the project's Metrics tab. See Agile Reports & Metrics.

Complete the sprint

1. Select the active sprint.
2. Select Complete Sprint.

The sprint moves to Completed and every ticket still unfinished goes back to the backlog, ready to be pulled into the next sprint or dropped.

Sprint length and estimating

The project's Settings tab sets two things that shape planning: Default sprint length in days under Cadence, and the estimation scale under Estimation — Fibonacci points or Time effort. Velocity window sets how many past sprints the average is taken over.