For a team of three to ten, sprint planning is one meeting of about an hour every two weeks. Before it, the backlog is groomed and estimated. In it, you agree one sprint goal, check how much capacity you really have after support and meetings, pull in work until the sprint is full, and stop. Everything else people associate with sprint planning is ceremony you can skip.
Most sprint planning advice is written for large organisations running a framework, where planning takes half a day and involves a dozen people. A team of five does not need that, and copying it is the fastest way to make everyone hate sprints. This guide covers what small teams actually need.
What you do before the meeting
Planning fails when the backlog is a surprise. Thirty minutes of grooming earlier in the week prevents the hour of confusion later.
- Pick the candidates. Whoever owns priorities chooses the items likely to be worked on next, in order.
- Make them understandable. Each one says what is wanted and how you will know it is done. If a developer cannot picture the first step, it is not ready.
- Size them roughly. Points, days or t-shirt sizes all work. Precision is not the aim; spotting the item nobody can size is.
- Split anything too big. If it cannot finish inside one sprint, it cannot be planned into one.
The hour itself, step by step
- Agree the sprint goal first, in one sentence. "Customers can reset their own password" beats a list of twelve tickets. The goal is what you protect when something goes wrong mid-sprint.
- Work out real capacity. Count working days, subtract leave, holidays, support duty and standing meetings. A team of five in a two-week sprint has fifty working days on paper and often nearer thirty in practice.
- Pull work in until the sprint is full. The team pulls, rather than having work pushed at it. Stop at capacity, not at the end of the wish list.
- Agree the first task for each person. Not a full assignment of everything, just enough that nobody leaves the meeting wondering what to start.
- Name the risks aloud. Who is waiting on whom, what depends on an outside answer, what nobody has done before.
The four mistakes that waste the hour
- Planning the whole sprint in detail. You are agreeing what to aim at, not writing a schedule. Detail added now is mostly rewritten by Wednesday.
- Ignoring support work. If two days a sprint go to bugs and customer questions, plan for two days a sprint. Pretending otherwise makes every sprint look like a failure.
- Filling capacity to one hundred per cent. Leave room. Something always arrives.
- Treating the commitment as a promise to management. It is the team's best judgement on the day. Punish a missed sprint and you will get padded estimates forever.
A checklist you can paste into your tool
- Sprint goal agreed, in one sentence
- Capacity calculated, with leave and support removed
- Every item has an owner for its first step
- Nothing pulled in that cannot finish this sprint
- Risks and dependencies named
- Carry-over from last sprint reviewed, not silently re-added
How to tell whether planning is working
You do not need a dashboard to know. Three signs tell you most of it: the team finishes close to what it planned most sprints, the sprint goal is still meaningful on the last day, and nobody is surprised at the review. If any of those fails repeatedly, the problem is usually grooming, not planning.
Charts help once you want the detail, and the two worth watching are explained in burndown vs velocity.
Where a tool helps, and where it does not
No tool fixes an unclear backlog. What a tool should do is make the sprint visible without anybody writing a status report: what was committed, what is in progress, what is blocked and how much is left.
WeTa loopin was built for this. You groom the backlog, estimate, set a sprint goal and commit as a team. Burndown and velocity update as the sprint runs, carry-over is handled rather than quietly forgotten, and retro notes stay attached to the sprint they belong to. It is free for up to 3 users, so a small team can try a full sprint before deciding anything.
Frequently asked questions
How long should sprint planning take for a small team?
About an hour for a two-week sprint, and rarely more than ninety minutes. If it runs longer, the backlog was not groomed beforehand, which is a grooming problem rather than a planning one.
How long should a sprint be for a small team?
Two weeks suits most teams of three to ten. One week gives faster feedback but means planning every week, and anything beyond three weeks tends to hide problems until it is too late to react.
Do small teams need story points?
No. Many small teams do better counting tasks, or sizing in days, or simply asking whether something fits in the sprint. Points only earn their place once you use them to forecast, and a team of four can usually forecast without them.
What should we do when work does not finish in the sprint?
Carry it over and look at why. One carry-over is normal. The same item carrying over three times means it was never properly understood, so break it down rather than moving it again.
Who decides what goes into the sprint?
The team commits, after the person responsible for priorities explains what matters most. If someone outside the team decides the contents, it stops being a commitment and becomes a schedule, and nobody defends a schedule they did not agree to.
Run your next sprint in WeTa loopin
Boards, sprints, burndown and releases in one place. Free for up to 3 users, so you can try a full sprint first.
Request a Demo Download the WeTa loopin brochure