Planning guide: agreeing what we will work on next (Scrum: sprint planning)
I developed this agile sprint planning guide to give facilitators, scrum masters and team leads something practical to pick up and use: a guide, a script and a short graphic novel for running a planning session. They have been used across enterprise transformation engagements in pharmaceuticals, FMCG and healthcare, and they are free to download here.
Planning is the session where a team agrees what it will work on next and how it will start. Scrum calls it sprint planning, and this page uses “timebox” where Scrum says “sprint”: a timebox is the fixed stretch of time we plan and work in. Done well, planning aligns the team on a shared goal, brings dependencies to the surface before they become blockers, and builds the kind of commitment that holds when plans change part-way through. Done poorly, it becomes a negotiation over tasks that leaves the team misaligned and the facilitator exhausted.
Each of the three gives the facilitator a structure to follow, so that the conversation gets the team’s full attention. For the definitive framework on sprint planning, refer to the Official Scrum Guide.
All three are free to download as PDFs. No credit is needed when you use them with your own team. If you republish them or share an adapted version, they are licensed CC BY-SA 4.0: credit Kubair Shirazee and share your version on the same terms.

What is in the planning pack
Planning guide. Four pages. It sets out why we plan, what we bring and what we leave with, then gives two checklists: seven things to do in the days before planning, and nine for the day itself. It closes with a worked example of a timebox goal and the list of things to do that backs it, using a weekend spent clearing out a garage. Use it on its own or alongside the script.
Planning script. Words you can say, step by step. It starts with preparing the room, then takes you through eight steps, from setting the stage and reviewing the roadmap to breaking tasks down, agreeing what “ready” and “done” mean, checking the plan is feasible and closing. Each step has its objective, a line to say and a tip for adapting it, and the last section covers what to do when a few voices dominate. As timed, the steps add up to 45 to 60 minutes, plus 5 to 10 beforehand to prepare the room, for a team of ten or fewer facilitated by one of its own members.
Planning day, the graphic novel. One page and eleven panels. Facilitator Fred and his team run a planning session from the product owner sharing the goals for the timebox to the team agreeing what done means. Use it to introduce planning to a new team or a new team member, or to make the ideas stick in a way that a page of text rarely does.
How to use them
The three are designed to work together, and each is useful on its own.
If your team is new to planning, start with the graphic novel, because it gives everyone the same picture before the first real session. Move to the planning guide for the preparation and the checks on the day, and keep the script beside you in the room.
If you already run these sessions and want to tighten planning in particular, the script is the fastest place to start. If you are building a team’s alignment from scratch, pair the planning guide with the team agreements resources on this site: a team with a clear agreement runs a better planning session. The invite for planning, written as a short charter, is on the agile meeting agenda template page.
Who they are for
Scrum masters, agile coaches and internal transformation leads who facilitate planning with their teams, and team leads new to agile who want a structure to follow while they build confidence as facilitators.
I built these for practitioners working inside complex organisations, where planning has to hold its own against competing priorities, unclear ownership, and teams that span several functions or countries. The structures work in those conditions because they were developed in them.
If you are working on a wider agile enablement or enterprise transformation programme and want to talk about facilitation beyond these downloads, get in touch directly.
Planning needs a fixed boundary to work against: see Working in Time Boxes. Close the cycle with a retrospective.
Planning: common questions
What is sprint planning?
Sprint planning is the session where a team agrees a goal for its next timebox, the fixed stretch of time it plans and works in, and chooses the work that will meet that goal. Scrum calls the timebox a sprint. The whole team takes part: the product owner or manager, the scrum master or project manager, and the people doing the work.
What is in the planning pack?
Three free PDFs by Kubair Shirazee: a four-page planning guide with checklists for before and during the session, a facilitator script with words to say at each of eight steps, and a one-page graphic novel called Planning day.
How long does a planning session take?
The eight steps in the script add up to 45 to 60 minutes, plus 5 to 10 minutes beforehand to prepare the room, for a team of ten or fewer.
Who are they for?
Scrum masters, agile coaches and internal transformation leads facilitating planning sessions, and team leads new to agile who want a structured approach.
Are they free?
Yes. All three are free to download as PDFs. They are licensed CC BY-SA 4.0: you can use and adapt them if you credit Kubair Shirazee and share your version on the same terms.