.png?fit=max&auto=format&n=V5LGcGniNC1X_QJO&q=85&s=8c9ba3ce9a0d0045976180c9f669af26){kind=logo}
Sprints
Sprints let you group tasks into time-boxed iterations — typically one to two weeks. Each sprint has a defined start date, end date, and an optional goal. When a sprint starts, the committed story points are snapshotted so you can detect scope changes over the course of the sprint.Sprint lifecycle
Creating a sprint
1
Open the Sprint view
Navigate to your project and select the Sprints view from the top navigation.
2
Create a new sprint
Click + New Sprint above the sprint list. A new sprint card appears in Planned status.
3
Set the sprint details
Give the sprint a name (e.g., “Sprint 14 — Billing Module”). Set the start date and end date. Add a sprint goal if your team uses them.
4
Add tasks
Drag tasks from the Backlog into the sprint panel. Alternatively, open individual tasks and set their Sprint field directly.
Sprint fields
Starting a sprint
1
Review the sprint scope
Confirm all tasks intended for the sprint are included. Check story point totals against team capacity.
2
Click Start Sprint
On the sprint card, click Start Sprint. A confirmation dialog appears showing the number of tasks and total story points.
3
Confirm activation
Confirm to activate the sprint. The sprint moves to Active status and the committed story points are snapshotted. Any tasks added after this point are counted as scope creep.
Collabase records the committed story points at the moment the sprint starts. If tasks are added later, the burndown chart reflects the original commitment separately from the added scope.
Running a sprint
While a sprint is active, the board and sprint view show only the tasks in that sprint. The sprint header displays:- Remaining tasks — tasks still in a non-Done status
- Completed tasks — tasks in a Done-category status
- Days remaining — countdown to the sprint end date
- Sprint goal — displayed at the top for team alignment
Burndown chart
The burndown chart tracks how many story points remain each day of the sprint. It shows:- Ideal burndown line — a straight diagonal from the committed point total at day one to zero at the end date
- Actual burndown line — the real story points remaining each day based on completed tasks
Completing a sprint
1
Click Complete Sprint
At the end of the sprint period, click Complete Sprint on the active sprint card.
2
Handle incomplete tasks
A dialog shows all tasks that did not reach a Done status. Choose to move them to the backlog or to a specific upcoming sprint.
3
Review the sprint summary
After completing, a sprint review summary is generated showing: total tasks completed, story points delivered, velocity for this sprint, and a comparison to recent sprints.
Velocity tracking
Velocity is the average number of story points completed per sprint, calculated across the last six completed sprints. It is shown in the Sprint view’s velocity chart. Use velocity to set realistic sprint goals. If your team consistently completes 40 story points per sprint, planning a sprint with 60 points will likely result in carry-over.Subtasks and sprints
A project can keep parent and child tasks together when their sprint changes, using two settings under Project settings → Cycles:
If Carry child work items is off but the parent task is in a sprint, creating a subtask shows a short prompt offering to add the new subtask to that sprint, so it is never placed there without your say-so. These behaviours are only available to members who are allowed to manage sprint scope (see below).
Who can manage sprints
Sprint management actions are restricted by the space’s Permission Scheme.The default Open Scheme allows Members to create and start sprints. The Default Software Scheme restricts these actions to Managers only. Your space may use a custom scheme with different settings — check with your Space Admin if you are unsure what applies.