> ## Documentation Index
> Fetch the complete documentation index at: https://docs.collabase.ch/llms.txt
> Use this file to discover all available pages before exploring further.
> Group tasks into time-boxed iterations. Plan, run, and review sprints with burndown charts, velocity tracking, and story points.
# Sprints
# 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
| Status | Meaning |
| ------------- | ---------------------------------------------------------------------------------------------------------- |
| **Planned** | Sprint is created and tasks are being added. Not yet active. Multiple planned sprints can exist at once. |
| **Active** | Sprint is underway. Only one sprint can be active at a time. Story points are snapshotted at activation. |
| **Completed** | Sprint is closed. Incomplete tasks are moved to the backlog or the next sprint. Velocity data is recorded. |
## Creating a sprint
Navigate to your project and select the **Sprints** view from the top navigation.
Click **+ New Sprint** above the sprint list. A new sprint card appears in Planned status.
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.
Drag tasks from the Backlog into the sprint panel. Alternatively, open individual tasks and set their Sprint field directly.
## Sprint fields
| Field | Description |
| -------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Name** | Descriptive label for the sprint, e.g., "Sprint 12 — Auth Hardening". |
| **Start Date** | The date the sprint begins. |
| **End Date** | The sprint deadline. Used to calculate days remaining. |
| **Goal** | Optional plain-text description of what the sprint aims to achieve. Shown at the top of the Sprint view during the sprint. |
## Starting a sprint
Confirm all tasks intended for the sprint are included. Check story point totals against team capacity.
On the sprint card, click **Start Sprint**. A confirmation dialog appears showing the number of tasks and total story points.
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
Team members move tasks through status columns as work progresses. The burndown chart updates as tasks are completed.
## 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
When the actual line is above the ideal line, the sprint is at risk of not completing on time. When it is below, the team is ahead of schedule.
## Completing a sprint
At the end of the sprint period, click **Complete Sprint** on the active sprint card.
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.
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.
Completing a sprint is final. Incomplete tasks are moved out of the sprint immediately. If you need to extend the sprint, update the end date before clicking Complete.
## 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.
| Metric | Description |
| --------------------- | ------------------------------------------------------------------------------ |
| **Velocity** | Average story points completed per sprint (last 6 sprints). |
| **Health: On track** | Actual burndown is at or below the ideal line. |
| **Health: At risk** | Actual burndown is above the ideal line but within range. |
| **Health: Off track** | Sprint is significantly behind — unlikely to complete on time at current pace. |
***
## Subtasks and sprints
A project can keep parent and child tasks together when their sprint changes, using two settings under **Project settings → Cycles**:
| Setting | What it does |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Carry child work items** | When a task moves in or out of a sprint, its subtasks move with it. It also applies when you create a new subtask under a task that is already in a sprint — the subtask is placed in the same sprint automatically. |
| **Carry parent work item** | When a subtask moves in or out of a sprint, its parent task moves with it. |
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.
| Action | Space Admin | Manager | Member | Viewer |
| ----------------------------- | ----------- | ------- | ------ | ------ |
| Create sprints | Yes | Yes | No | No |
| Start a sprint | Yes | Yes | No | No |
| Complete a sprint | Yes | Yes | No | No |
| Edit sprint name, goal, dates | Yes | Yes | No | No |
| Delete sprints | Yes | No | No | No |
| Add tasks to a sprint | Yes | Yes | Yes | No |
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.