Sprint planning that carries the rest forward.
Turn sprints on for the boards that need them and plan each one against its capacity. Unfinished work moves to the next sprint, on its own when sprints run on a schedule, and the running sprint’s burndown, velocity and scope change show how the work is going.
Sprints are a setting, not a methodology
A board runs sprints only when an admin turns them on in the board settings, so a support board can stay a plain Kanban while the product board works in two-week cycles. Turning them off later keeps the sprints and their cards on record.
On a schedule
Pick a length of one to four weeks and the weekday sprints start. Once the first sprint is planned, TaskDeck closes each sprint after its last day, starts the next one and keeps one planned ahead, with nobody pressing a button.
By hand
Plan a sprint, start it when the team is ready and complete it when you decide. Useful when cycles follow releases rather than the calendar.
Plan against capacity
- The Planning view puts the backlog beside the sprint: drag cards across, or press Plan and Unplan
- Set the sprint's capacity as time, such as 40h; the total of the estimates keeps up and warns when you are over
- New cards join the running sprint as they are created
- The board shows the sprint with its dates, days left and how much of the estimate is finished
Close the sprint without losing anything
When a sprint ends, everything unfinished moves to the next sprint, or back to the backlog if you choose. Each card counts how many times it has carried over, and a card carried more than once is marked in red so it gets a conversation instead of another ride.
Look back with numbers
- Burndown
- The estimate left on each day of the running sprint against the ideal line, from a snapshot taken every day. A card counts as finished in any column marked as finished, or once it is closed.
- Velocity
- The estimate finished in each of the last eight sprints, with the median marked, so planning starts from what the team really does.
- Scope change
- What joined and left each sprint after it began, and what carried over when it closed.
Sprints reach the rest of TaskDeck
- The Timeline draws a band for every sprint behind the cards' dates
- My activity shows the running sprint with its days left and open cards
- Slack channels and webhooks hear when a sprint starts and when it is completed
- AI agents can create sprints and plan cards into them, while starting or completing a sprint comes to a person as a plan to approve
Sprints
Questions about sprints
Do I have to use sprints?
No. Sprints are off until an admin turns them on for a board, and each board decides for itself.
What happens to unfinished cards when a sprint ends?
They move to the next sprint, which TaskDeck creates if none is planned, or back to the backlog if you choose that when completing. Each card keeps count of how often it carried over.
Can sprints start and end automatically?
Yes. On a scheduled board a daily run closes each sprint once its end date has passed, starts the next one and carries unfinished work over.
Which plans include sprints?
All of them, the Free plan included. Sprints, burndown, velocity and scope change are not limited by plan.
Give your next project a clear starting point.
Create a board, add your first task, and bring your team together.
No credit card required · Free forever plan