Mind map template · Technical
Sprint planning template, as a mind map
Plan the sprint on one map: a goal in one sentence, the capacity you really have, the stories you commit to, and what counts as done.
Shiko is in closed beta: this takes you to the wishlist first.
The template as it opens. Every prompt is a node you answer under or replace.
What's inside
Sprint name
- Sprint goal
- One sentence: what will be true at the end of the sprint?
- Capacity
- Team members and days available
- Time off and holidays
- Velocity: average points from recent sprints
- Committed work
- User story: as a user, I want… (a task list)
- User story: as a user, I want… (a task list)
- User story: as a user, I want… (a task list)
- Bugs
- Bugs to fix (a task list)
- Tech debt
- Debt to pay down (a task list)
- Risks and dependencies
- What could block us?
- Who do we depend on?
- Definition of done
- A story is done when… (a task list)
- Stretch
- Work we take on only if we finish early
How to run it with your team
- Write the sprint goal firstOne sentence: what will be true at the end of the sprint? Everything else on the map should serve it.
- Check capacity before committingUnder Capacity, list who is available, time off and your recent velocity, so the plan fits the team you actually have.
- Commit the work as tasksCommitted work, Bugs and Tech debt are task lists, each with its own owner and due date. Anything that does not fit goes under Stretch.
- Name the risks and agree on doneWrite what could block you and who you depend on, then the definition of done every story has to meet.
What is sprint planning?
Sprint planning is the meeting that starts each sprint in Scrum. The team agrees why the sprint matters (the sprint goal), what it will deliver from the backlog, and how it will get the work done. The Scrum Guide caps it at eight hours for a one-month sprint; for a two-week sprint most teams need an hour or two.
A good sprint planning meeting starts from capacity, not from the backlog: who is around, who is on holiday, and how much the team usually finishes. Then the team picks the stories that serve the goal, makes sure each has acceptance criteria, and leaves room for bugs and tech debt. A shared definition of done keeps "finished" from meaning different things to different people.
The people doing the work should set the scope. On a mind map the whole plan is visible at once, everyone can add to it during the call, and work that does not fit has an obvious place: Stretch.
When to use it
At the start of each sprint, with the whole team in the room or on a call. Use it as an agile sprint planning template or a plain sprint template: planning together on one map means the people doing the work set the scope, not one person in a spreadsheet.
It pairs with the retrospective template: the actions from your last retro become stories or tech debt here.
Questions
Can my whole team edit it at once?
Yes. Everyone you invite works on the same map live, and you see who is typing where.
What does a sprint plan example look like?
Sprint goal: new users can invite a teammate. Capacity: four developers, one off on Friday, about 30 points. Committed work: the invite form, the invite email and accepting an invite, each with its acceptance criteria. Bugs: two from the last release. Stretch: a reminder email.
Can tasks have owners and due dates?
Yes. Each task list takes an owner, a due date and a priority, and shows how many of its items are done.
Does it replace our issue tracker?
No. It is for planning the sprint together; keep detailed tickets wherever your team already keeps them.