Sprint Planning: Starting the Sprint right
Sprint Planning is where the team comes together as one. Not a collection of individuals with separate tasks, but a team with a shared goal, a shared plan, and a shared commitment to deliver.
When it works, that's exactly what it feels like.
What is Sprint Planning?
Sprint Planning is the first event of every Sprint. Its purpose is simple: create a realistic Sprint Plan the team can commit to.
The whole Scrum Team - Scrum Master, Product Owner and Developers - shapes the plan together. The result is a Sprint Backlog: a Sprint Goal, a set of selected work, and a plan for delivering it.
Sprint Planning is the moment a group of individuals becomes a team with a shared mission. The shift - from "here's what I'm doing" to "here's what we're delivering together" - is what makes the difference between a Sprint that delivers and one that drifts.
Every one of these shifts moves the dial on team performance. You can measure that with the 3V Net Performance Score - CoLab's way of tracking how your team is really doing.
Grounded in the Scrum Guide and the Agile Manifesto. This RAFT is CoLab's take on how to make it work in practice.
What we focus on
Start fresh
The Sprint Backlog starts empty every Sprint. That discipline forces the team to re-evaluate what matters now. Unfinished work from last Sprint goes back to the Product Backlog and gets reprioritised. It might still be the most important thing. It might not be. The team decides together.
Confirm WHO's in
Before the team commits to anything, check who's actually available. How many days does each person have? Account for leave, public holidays, ceremonies and anything else that will eat into delivery time. Capacity is a team conversation, not a guess. A team that knows its real capacity commits with confidence.
Agree the WHY
The Sprint Goal is the single most important output of Sprint Planning. It should describe why this Sprint is valuable - not summarise the list of items. A good Sprint Goal gives the team something to orient around when the unexpected happens, which it always does. Agree it together, write it down, put it somewhere visible. This is the team's shared mission for the Sprint.
Pull the WHAT
The team selects work from the top of the Product Backlog in conversation with the Product Owner. Before pulling anything in, it's worth asking: is this item actually ready? Many teams find it useful to agree a Definition of Ready - a shared understanding of what a backlog item needs before it can be pulled. It prevents a lot of mid-Sprint stalling and keeps the team moving together.
Plan the HOW
The Developers plan their own work. That's not just a Scrum rule - it's where commitment comes from. When the team works out the how together, you get ownership, creativity and collective problem solving. The team also needs a shared Definition of Done - if done means different things to different people, the commitments aren't real.
Commit carefully
Stop when the team can't take on more. A team that commits carefully and delivers is far more valuable than a team that promises everything and delivers half. This is the team holding itself to a standard together - not individuals saying yes to please, but a team being honest about what it can achieve.
Why We Love It
Done well, Sprint Planning:
Gives the Sprint a shared purpose. The Sprint Goal isn't a summary of the work - it's the reason the work matters. When the whole team helps shape it, everyone understands what they're playing for.
Creates real commitment. When the team selects their own work and plans the how together, they own it. That's a very different energy from being assigned a task list.
Starts with a clean slate. Beginning with an empty Sprint Backlog forces the team to ask what matters most right now - not just carry on with whatever's left over.
Connects individual effort to collective outcome. A clear Sprint Goal means the team can make good decisions throughout the Sprint without needing constant direction.
Builds confidence before the Sprint starts. A realistic plan - one the team has shaped together with eyes open on capacity - means the Sprint begins with momentum rather than anxiety.
When We Use It
Sprint Planning happens at the start of every Sprint. But the quality of it varies enormously from team to team. We pay extra attention to how a team plans when:
A new team is forming and needs to build the habit of planning and committing together.
The team keeps missing their Sprint Goal and nobody's quite sure why.
The Sprint Backlog is consistently overloaded and the team is always chasing its tail.
There's no real Sprint Goal - just a collection of items with no connecting thread.
Unfinished work is rolling over Sprint after Sprint without being questioned.
How We Do It
There are five key phases that make an Innovation Day work. Skip one and the energy turns to confusion quickly.
Prepare. Gather ideas upfront - a simple survey works well. Turn the best ones into short 1-page canvases. Get a small group of people aligned on the goals before the event starts.
Prioritise. Share the pitches with senior stakeholders. Get their support for the most viable ideas. This step is what separates a credible event from a fun day out.
Form teams. Give people a genuine choice of project. Teams of five to eight work well. Getting people in the same room makes a noticeable difference to how fast collaboration clicks.
Run the event. Two days works. Three days is better - it gives teams time to get stuck, unstick themselves, and actually finish something. Kick off with leadership framing why it matters. External coaches or vendor partners can help teams stay focused.
Present and recognise. Teams present to leadership with a focus on business value. Finish with recognition and prizes. This is what people remember and what builds appetite for next time.
Things to Look Out For
The Sprint Goal gets written at the end as an afterthought rather than agreed first. It should anchor everything else.
Capacity gets eyeballed rather than checked. Five minutes on a simple capacity check at the start of planning can save a Sprint.
Items get pulled without being ready. If the team spends the first two days of a Sprint trying to understand what they committed to, something wasn't ready.
Sprint Planning becomes a presentation by the Product Owner rather than a conversation with the whole team. The whole team shapes the plan - that's what makes it a commitment rather than an instruction.
Try It With Your Team
If your Sprint Planning feels like it's going through the motions, start with the Sprint Goal. Before you select a single item, agree what this Sprint is actually trying to achieve. Write it down, put it somewhere visible, and come back to it throughout the Sprint.
The capacity planning template below gives you a simple way to check real availability before the team commits to anything. It takes five minutes and can save a Sprint.
Track whether it's making a difference with the 3V Net Performance Score.
Download the free Sprint Planning capacity template and give it a go.
Our RAFT Series
✦ Sprint Planning is one of our CoLab RAFTs - Rapid Agile Forecasting & Tracking techniques. Practical tools we use every day in our coaching and training to help teams make work visible and performance-focused.
Updated on 10 April 2026
