Sprint planning template, from goal to done.
Everything a planning meeting needs on one page: the sprint goal, team capacity, committed work with points and owners, risks, and a shared definition of done. Copy it or download the Markdown file. It is free, no sign-up needed.
# Sprint planning: Sprint [number] Dates: [Start] to [End] Length: [1 / 2] weeks Team: [Names] Capacity: [Total story points or hours available, after time off] ## Sprint goal [One sentence the whole team can repeat: what will be true at the end of this sprint?] ## Carried over from last sprint - [Task] - [Points] - [Why it rolled over] ## Committed work | Task | Type | Points | Owner | Notes | | --- | --- | --- | --- | --- | | [Task] | Feature | 3 | [Name] | | | [Task] | Bug | 1 | [Name] | | | [Task] | Chore | 2 | [Name] | | Total committed: [Sum] points of [Capacity] ## Stretch work (only once committed work is done) - [Task] - [Points] ## Risks and dependencies - [Risk or dependency] - [Owner] - [Plan] ## Definition of done - [ ] Code reviewed and merged - [ ] Tested - [ ] Docs or changelog updated - [ ] Demoed to the team ## Planning checklist - [ ] Top of the backlog groomed and estimated - [ ] Capacity accounts for time off - [ ] Every committed task has an owner - [ ] Sprint goal agreed by the team
Three habits that make it actually work.
Agree the goal before the tasks.
A sprint goal the whole team can repeat makes it easy to say no to work that does not serve it.
Plan to capacity, not to hope.
Subtract time off and meetings first, then commit. Put extra work in the stretch list instead of the commitment.
Look at what rolled over.
Carried-over work tells you whether estimates or scope need a change before you plan the next sprint.
Run the sprint in Dutify Cloud
- Native sprints. Sprint groups, story points, task rollover, auto-start and a burndown chart, built in.
- Every view you need. List, board, table, calendar and Gantt views, custom fields, automations and time tracking with estimates vs. logged time.
- AI agents on the same board. Connect Claude, ChatGPT, Cursor or your own agent through the MCP server with scoped keys, and let it work on the same tasks your team sees.
Three tools, one subscription.
Every plan includes Dutify Cloud, Codexum and Roadmarq.
Projects and sprints
List, board, table, calendar and Gantt views, custom fields and automations.
Team wiki
Docs your team and your AI tools can search, with permissions per space and page.
Feedback and roadmap
Feature requests, voting without an account, a public roadmap and changelog.
Questions
What is a sprint planning template?
A one-page structure for the planning meeting at the start of a sprint: the goal, the team’s capacity, the work the team commits to, risks, and the definition of done.
How long should sprint planning take?
A common rule of thumb is about two hours per week of sprint, so up to four hours for a two-week sprint. A groomed backlog makes it much shorter.
Can I run sprints in Dutify Cloud?
Yes. Dutify Cloud has native sprints with story points, sprint groups, rollover of unfinished tasks, auto-start and a burndown chart. Paid plans start at $4.80 per user per month billed annually, and the Codexum wiki and Roadmarq feedback boards are included.
Skip the blank page with Dutify Cloud
Start free and keep this structure next to the work it belongs to.