Planning sprints and tracking velocity
Sprints are time-boxed iterations (usually 1–2 weeks) where your team commits to a set of work. ProTasks tracks story points, velocity, and burndown automatically — no spreadsheets required.
Sprints & Velocity
Track iteration progress · forecast capacity
Creating a sprint
- 1
Open your board and click the Sprints icon in the sidebar.
- 2
Click 'New sprint' and give it a name (e.g. 'Sprint 15').
- 3
Set a start and end date — most teams use 2-week cycles.
- 4
Write a sprint goal — one sentence describing what success looks like.
- 5
Save. The sprint is now 'Planned' and ready to fill.
Keep sprint names sequential (Sprint 14, 15, 16…) so velocity charts stay readable.
Adding tasks and story points
Open any task and set its 'Sprint' field to your new sprint. Add 'Points' — a quick estimate of effort (1, 2, 3, 5, 8 are typical).
The sprint's 'Committed points' updates automatically. As tasks move to Done, 'Completed points' tracks alongside.
Starting and ending a sprint
- 1
When ready, change the sprint status from 'Planned' to 'Active'.
- 2
Only one sprint should be active at a time per board.
- 3
At the end of the cycle, set it to 'Completed'. Any unfinished tasks can be pulled into the next sprint.
Reading the velocity chart
The velocity chart shows committed vs. completed points across recent sprints. Look for trends:
- 1
Consistent completion ≈ commitment → healthy, predictable team.
- 2
Committed always higher than completed → you're over-promising. Trim scope.
- 3
Velocity climbing → team is gelling or scope is shrinking. Confirm which.
- 4
Big drop → look for blockers, holidays, or shifts in team size.
Use the average of your last 3 sprints as your capacity for the next one. It's a better predictor than gut feel.
Sprint reviews and retrospectives
At the end of each sprint, review what shipped (Done tasks) and what didn't. The sprint goal card on the dashboard makes this a 2-minute exercise. Capture lessons in the Resources hub or a wiki page so they compound over time.
