Skip to content

Sprint planning for small teams

A sprint is a fixed stretch of time with a short list of work. For a team of two to ten, one hour of planning and thirty minutes of review is enough.

Written by the BugBoard team. 6 minute read. Updated 16 November 2026.

Pick a length and keep it

One week suits a team that ships often and has few dependencies. Two weeks suits a team that needs time to finish bigger pieces. Pick one, keep it for at least six sprints and then judge. Changing the length every sprint makes your numbers useless.

Work out capacity

Capacity is how much work the team can really do, not how many days are on the calendar. Start from working days, take out leave and public holidays, and then take out the time that is not sprint work: support, meetings, review of other people’s work. Two thirds to three quarters of a day is a reasonable first guess. Replace it with your own history after three sprints.

PersonDays in sprintAwayShare on sprint workCapacity (days)
Ana10070%7
Ben10270%5.6
Chris10050% (on call)5
Team30217.6

Pick the work

  1. Start with what was carried over. It is already started, so it costs less than it looks and more than you want.
  2. Add the fixes that are urgent by your own priority definition.
  3. Add the one goal that matters most, written as a sentence a customer would understand.
  4. Estimate the rest in days, or in points if your team already uses them. Round up.
  5. Stop at about 80% of capacity. The sprint will contain surprises.

If a task is bigger than half the sprint, split it before it goes in. If nobody can say how long it will take, put a short investigation in the sprint instead of the task.

A planning agenda to copy

Sprint planning, <team>, sprint <n>, <start> to <end>
Time: 60 minutes. Facilitator: <name>. Notes: <name>.

 0-10  Last sprint in one line: done, carried over, dropped
10-20  Capacity per person (table above), total in days
20-30  The goal, in one sentence
30-50  Pick the work, top down:
         carried over, urgent fixes, goal work, the rest
         each task has an owner and an estimate
50-55  Check: total <= 80% of capacity? Anything blocked by
         someone outside the team?
55-60  Read the list aloud. Agree. Stop.

Output: goal, list of tasks with owners, risks

Changes in the middle of a sprint

  • An urgent item comes in: it goes in, and something of the same size goes out. Say which, and write it down.
  • A task turns out bigger: tell the team the same day, and split it. Do not keep working on a task that has quietly doubled.
  • Someone is away: reduce the plan, not the hours of the others.
  • The goal stops mattering: end the sprint early and plan again. This is rare. If it happens often, the sprint is too long.

Review and retrospective

End with thirty minutes. Spend ten on what was done and show it, ten on what was not and why, and ten on one change to try next sprint. One change, not five. Write it at the top of the next plan, and check it then.

What to measure

  • Done against planned, as a count of tasks. A trend over four sprints says more than any one number.
  • Carried over, as a count. If it keeps rising, you plan too much.
  • Work added during the sprint. If it is more than a fifth of the plan, your priorities are not stable, or the sprint is too long.
  • Do not compare people, and do not compare teams. The numbers belong to the team that made them.

How BugBoard’s sprints work

Sprints are on the Starter plan and above. On Free you can still read past sprints, but you cannot start or end one. Each task sits in the backlog, in “next” or in “current”. Starting a sprint moves the tasks in next to current, and you pick the planned end date. A project has one active sprint at a time. Ending it keeps a record of how many tasks it carried and how many were done, sends unfinished tasks back to next, and clears the finished ones. The dates show on the calendar view and can be dragged.

BugBoard does not work out capacity for you, so keep the capacity table in your planning notes. The sprint view shows a burndown line, but its actual line is a straight glide from the committed work to today’s remaining work, because daily snapshots are not stored yet. Read it as a rough guide, not as a measurement, and rely on your own done, carried-over and added counts.