Project management · Practical guide
Sprint Planning: Capacity, Scope and a Clear Goal
By My First Task editorial team
Updated
The short answer
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
- Write a sprint goal that describes an outcome rather than a task count.
- Calculate team availability after leave and known non-project commitments.
- Review the most important backlog items and identify blocking dependencies.
- Agree acceptance criteria and split items too large to complete within the sprint.
- Select work with room for uncertainty, assign owners and record what is excluded.
- 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?
What is a useful sprint goal?
Can I plan without story points?
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
Project Status Report Template: Progress, Risks and Decisions
A project status report summarizes progress toward an outcome for a stated reporting period. Include completed deliverables, upcoming commitments, risks, changed dates and decisions needed, with an owner for each follow-up.
ExploreProject Kickoff Checklist and Meeting Agenda
A project kickoff aligns the people doing and approving the work on the outcome, scope, roles, constraints and first decisions. Finish with an agreed brief and owned next actions, rather than treating attendance as evidence of alignment.
ExploreScope Creep: Examples and a Practical Change Checklist
Scope creep is growth in project work without an explicit agreement about its effect on time, cost or the intended outcome. Manage it by documenting the baseline, recording proposed changes and making the trade-off visible before accepting more work.
ExploreTurn 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.