Sprints

Sprints are time-boxed iterations (typically 1-4 weeks) where the team commits to completing a set of tasks from the backlog. Each sprint follows a defined lifecycle from planning through completion.

Sprint Lifecycle

stateDiagram-v2
    [*] --> PLANNING
    PLANNING --> ACTIVE : Start sprint
    ACTIVE --> COMPLETED : End sprint
    COMPLETED --> [*]

Creating a Sprint

1. Navigate to Tasks > Sprints
2. Click New Sprint
3. Configure the sprint:
   • Name -- e.g., Sprint 14 or March Week 1
   • Start date -- when the sprint begins
   • End date -- when the sprint ends
   • Goal -- what the team aims to achieve this sprint
   • Project -- the project this sprint belongs to
4. Click Save

The sprint starts in PLANNING status.

Sprint Planning

During planning, pull tasks from the backlog into the sprint:

1. Open the sprint in PLANNING status
2. Browse the backlog for prioritized tasks
3. Drag tasks into the sprint or use the Add to Sprint action
4. Review the sprint scope against team capacity
5. When ready, click Start Sprint to move to ACTIVE

Only one sprint per project can be ACTIVE at a time.

During the Sprint

While a sprint is active:

• Use the Board view to track task progress across status columns
• Update task statuses as work progresses (TODO, IN_PROGRESS, IN_REVIEW, DONE)
• The burndown chart updates daily to show remaining work
• New tasks can be added mid-sprint if scope changes are agreed upon

Completing a Sprint

When the sprint end date arrives or all work is done:

1. Click Complete Sprint
2. Review the sprint summary:
   • Tasks completed vs. planned
   • Velocity (story points completed)
   • Incomplete tasks
3. Choose what to do with unfinished tasks:
   • Move to the next sprint
   • Return to the backlog
4. The sprint moves to COMPLETED status

Velocity Tracking

Velocity is tracked across completed sprints to help with future planning. The system records story points completed per sprint and displays trends over time. See the Analytics page for details.