A hiking app team's plan of ten tasks across six two week sprints
Sprint plan slide with ten tasks, six sprints and an owner on each bar
A sprint plan slide shows which pieces of work land in which two week sprint, and who owns each, so a team and its stakeholders agree on the next three months. This one plans version 3.0 of Trailwick, a fictional hiking app, from 1 March to 21 May 2027.
What is on the slide
- Title
- Trailwick 3.0 Sprint Plan
- Framing line
- Ten tasks over six two week sprints, 1 March to 21 May 2027. Every bar names its owner.
- Design
- Design system update, sprint 1, Aroha. Usability tests, sprint 3, Aroha.
- Backend
- Route sync API, sprints 1 to 2, Priya. Offline map tiles, sprints 2 to 4, Tomas. Elevation service, sprints 3 to 4, Priya.
- Frontend
- New trail screen, sprints 1 to 3, Mei. Offline download UI, sprints 3 to 5, Jonah. Route sharing, sprints 4 to 5, Mei.
- QA
- Regression suite, sprints 4 to 6, Sam. Beta release, sprint 6, Sam.
When this is the right slide
Right when a delivery team and its stakeholders need to agree which of up to ten features lands in each of six two week sprints, and who owns each one.
What to swap it for
Grouping: 3 Kanban Swimlanes. When the meeting is about the current state of work, to do, in progress and done, rather than its timing.
What this slide shows
The title reads Trailwick 3.0 Sprint Plan, with the framing line: ten tasks over six two week sprints, 1 March to 21 May 2027, every bar names its owner. A Gantt fills the slide with columns Sprint 1 to Sprint 6 and ten striped rows, each with a task name and its team underneath. Design system update, Design, sprint 1, Owner: Aroha. Route sync API, Backend, sprints 1 to 2, Owner: Priya. New trail screen, Frontend, sprints 1 to 3, Owner: Mei. Offline map tiles, Backend, sprints 2 to 4, Owner: Tomas. Usability tests, Design, sprint 3, Owner: Aroha. Elevation service, Backend, sprints 3 to 4, Owner: Priya. Offline download UI, Frontend, sprints 3 to 5, Owner: Jonah. Route sharing, Frontend, sprints 4 to 5, Owner: Mei. Regression suite, QA, sprints 4 to 6, Owner: Sam. Beta release, QA, sprint 6, Owner: Sam. Bars in the same team share a colour, though the theme has three bar colours for four teams, so Design and QA both appear in navy.
When this is the right slide
Use a sprint plan slide at quarterly or release planning, when a delivery team needs to agree with product managers, designers and stakeholders on what lands in each sprint and who owns it. It suits software teams working in two week sprints over about three months, with six to ten features rather than dozens of tickets. It is the wrong slide for a board or customer audience, who need a roadmap by quarter, and for a weekly stand up, where a board of current tasks is more useful than a three month chart. It also suits only teams that genuinely plan this far ahead; a team working from a continuous queue should not invent sprint dates for a slide. The slide also helps a team say no. When a stakeholder asks for a new feature mid quarter, the plan shows which bar would have to move or shrink, which makes the trade off visible instead of letting extra work quietly pile onto the same six sprints.
How to adapt it
First, replace the ten tasks with your own features, keeping each name to two to four words and the owner's first name in the bar. Second, group the tasks by team and order the rows by start sprint, so the chart reads as work flowing from left to right toward one release bar. Third, when the conversation is about where work stands this week rather than when it will finish, swap to the three kanban swimlanes layout, which shows to do, in progress and done. Whichever you use, update the slide at every sprint review; a plan shown once at kickoff and never again stops being trusted by sprint three. Keep bar labels to names rather than ticket numbers, since the people reading the slide may not have access to the tracker and should not need it to understand the plan.
What makes this slide work
Every bar names one owner
Owner: Aroha, Owner: Priya, Owner: Mei, Owner: Tomas, Owner: Jonah, Owner: Sam. Each of the ten bars carries a single first name instead of a description, so the slide answers the question stakeholders ask most often in planning: who do I talk to about this piece of work?
The plan ends on one clear outcome
The last bar is the beta release in sprint six, owned by Sam. Reading the chart from top to bottom and left to right, every task leads toward that bar, which gives the room a single finish line and makes it obvious when a slip in the backend would push the beta later.
Tasks are grouped by team and ordered by start
Design, Backend, Frontend and QA labels sit under each task name, and the rows are ordered by when work starts, from the design system update in sprint one to the beta release in sprint six. The staggered bars show the team ramping up and handing work along.
Questions people ask
How many tasks fit on a sprint plan slide?
This layout holds ten, which is its cap, and ten is about the most a room can follow. A real sprint backlog has dozens of tickets; the slide should show epics or features, not tickets. If a team has fifteen items, group the small ones into a single bar, such as bug fixes, and keep the backlog in the team's tracker.
Should a sprint plan show who owns each task?
Yes. One name per bar, as here, tells stakeholders who to ask and tells the team who is accountable. Owner: Priya on the route sync API means one person answers for it, even if three people work on it. Without owners, a sprint plan is a wish list that nobody feels responsible for.
Can a sprint Gantt show task dependencies?
This chart has no dependency arrows; bars sit independently in their rows. Show the most important dependency through the order of the bars, such as the route sync API finishing before route sharing starts, and mention it aloud. If dependencies drive the whole plan, a flowchart or a written risk note explains them more clearly.
How far ahead should a sprint plan go?
Six sprints, roughly three months, is a sensible horizon, and it is what this layout shows. Beyond that, plans change too much to be useful at sprint level. Use a quarterly roadmap for the longer view and update the sprint plan at each sprint review, moving bars as the team learns.
When should a sprint plan become a kanban board instead?
When stakeholders care about the state of work more than its timing. A kanban board shows what is to do, in progress and done right now. A sprint plan shows when things are expected. Many teams show the sprint plan at quarterly planning and the board at weekly check ins.
How do I present a sprint plan to stakeholders?
Start with the end: beta release in sprint six. Then walk the groups one at a time, design first, then backend, frontend and QA, naming owners as you go. Point out the one or two places where bars depend on each other. Close by asking whether anything on the plan conflicts with other commitments.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make one like thisOther slide examples
Product roadmap slide with eight items across four quarters
A product roadmap slide shows what a team plans to build over the coming year and roughly when, grouped by theme so the audience sees the shape of the plan rather than a backlog. This one lays out 2027 for Rostrel, a fictional rostering app, and says plainly which quarters are estimates.
Swimlane roadmap slide with one lane per team
A swimlane roadmap slide shows several teams' plans side by side over the same period, one lane per team, so leaders can see who is doing what and where the work overlaps. This one covers five quarters at Brindell Ledger, a fictional accounting software company, across four teams.
Implementation plan slide with a success measure for every phase
An implementation plan slide shows how a change will be rolled out in stages and what has to be true before each stage moves on to the next. This one sets out how Wyncliffe Aged Care, a fictional provider, moves 374 staff in four homes to a new roster system in 2027.
Want the steps in the builder? Read Add charts, maps and diagrams to slides, then Add, reorder and restructure slides. For everything this generator can do, see the slide maker.
Written and checked by the OneCraft team. Last checked .