Project management · Practical guide

Sprint Planning: Capacity, Scope and a Clear Goal

By My First Task editorial team

Updated

The short answer

Sprint planning selects a realistic slice of work that advances one agreed goal. Start with actual capacity, review dependencies and acceptance criteria, then commit to a coherent set of tasks rather than filling every available hour.

How to approach the work

A backlog is a list of possible work; a sprint plan is a specific agreement about what the team intends to finish next. Estimate leave, training, support and meetings before selecting tasks. Story points describe relative complexity, while capacity hours describe time. Keep those units separate. When priorities change mid-sprint, make the trade-off visible instead of silently adding another commitment.

A practical sequence

  1. Write a sprint goal that describes an outcome rather than a task count.
  2. Calculate team availability after leave and known non-project commitments.
  3. Review the most important backlog items and identify blocking dependencies.
  4. Agree acceptance criteria and split items too large to complete within the sprint.
  5. Select work with room for uncertainty, assign owners and record what is excluded.
  6. Revisit the plan when capacity or scope materially changes.

Illustrative scenario · not customer research

Worked example

A five-person team has ten working days at eight hours per day: 400 gross hours. Forty hours of leave leave 360 hours. Allocating 70% to planned work gives 252 focus hours. That percentage is an example assumption, not a recommended universal target. The team chooses a checkout-stability goal and selects the tests and fixes needed to achieve it. Optional UI polish stays in the backlog. If an urgent incident consumes a day, the team discusses which planned item moves out.

Common mistakes to avoid

  • Converting points into hours using a fixed ratio.
  • Counting partially finished work as completed velocity.
  • Treating the plan as immutable after availability changes.

Try the method with your own inputs

Questions answered

Should a sprint be planned to 100% capacity?
Plan from the team's actual history and obligations. Filling every scheduled hour leaves no allowance for uncertainty. There is no single buffer percentage appropriate for every team.
What is a useful sprint goal?
A useful goal describes the outcome the work should achieve, such as enabling customers to retry a failed payment. It helps the team decide which tasks belong in the plan.
Can I plan without story points?
Yes. You can use small, comparable work items and observed throughput, or time estimates with explicit uncertainty. Agree the method and avoid mixing units in one forecast.

Apply it in a shared workspace

Keep the agreed owner, completion criteria and important decisions with the work. Explore the relevant My First Task feature.

Research context is available in our source library. The worked example above is an editorial illustration.

Continue learning

Turn the plan into shared work

Give each next action an owner, a completion condition and a realistic date. My First Task brings tasks, boards, project workflows and issue tracking into one workspace.