Agile Delivery
Run sprints on the same tasks you already track — a backlog, sprint planning, a focused board, story points, velocity and a burndown that's computed for you, not maintained by hand.
Open a project and choose Sprints. You'll see the project backlog beside your sprints. Sprints organize the very same tasks as everywhere else — there are no separate "agile items" to keep in sync.
Backlog & Planning
Groom the backlog, size tasks in story points, then pull work into a sprint from the planning screen (or send it back to the backlog). Each sprint has a goal and start/end dates, and the planning view totals the committed points.
The Sprint Lifecycle
- Planning. Build the sprint from the backlog and set its goal.
- Active. Work the sprint board — a Kanban scoped to just this sprint's tasks.
- Completed. Close the sprint; unfinished tasks are carried back to the backlog automatically, so nothing is lost and metrics stay honest.
Velocity & Burndown
Because a sprint tracks real tasks, its metrics come straight from the data. Velocity sums the story points completed in each finished sprint and shows a rolling average — a grounded basis for forecasting. The burndown plots remaining work against the ideal line, computed from completion timestamps, so there is no nightly snapshot job to maintain or break.
| Metric | How it's derived |
|---|---|
| Velocity | Sum of completed story points per finished sprint, plus a rolling average. |
| Burndown | Remaining work vs the ideal line, from real task completion times. |
| Carry-over | Unfinished tasks returned to the backlog when a sprint completes. |
Prefer a scheduled, dependency-driven view? Use Planning & Gantt over the same tasks.
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.