May 19, 2026
6 min read
Capacity and sprint planning
How to Plan Capacity for Part-Time Team Members
A practical guide to planning sprint capacity when some team members are part-time, shared across teams, or only partly available for delivery work.
Start with usable availability, not headcount
The easiest mistake with part-time team members is counting people instead of counting actual delivery availability.
A team of six does not really behave like a team of six if one person is available two days a week and another is split across multiple teams.
Part-time capacity
Headcount hides part-time reality, so each person needs to be translated into usable sprint room.
Part-time reality
A person being on the team does not mean full sprint capacity is available.
Actual days
Plan from the real days and hours available in this sprint.
Shared specialists
Part-time contributors often create constraints beyond their own hours.
Indirect impact
Other teammates may lose flow while waiting on narrower availability windows.
Usable team view
Capacity planning gets better when each person's real room is visible before commitment.
Translate each person into real sprint room
Part-time contributors should be represented by the amount of sprint time they can genuinely give, not by a full-person placeholder that gets adjusted loosely later.
That means accounting for the actual days, hours, or percentage of sprint time they will spend on this team's work.
Do not forget the work around the work
Part-time availability usually shrinks even further once meetings, coordination, handoffs, and context switching are counted.
A person who is technically available for half the sprint may still have less than half a sprint of real focus time if their schedule is fragmented across teams or responsibilities.
Treat shared specialists carefully
Designers, QA specialists, DevOps support, or other shared roles often create hidden capacity assumptions because several teams quietly expect the same person to be more available than they really are.
If a part-time or shared specialist is important to delivery flow, their real availability needs to shape the commitment early.
Watch the indirect effects on the rest of the team
Part-time coverage does not just reduce one person's output. It can change review timing, collaboration speed, and handoff friction for the rest of the team too.
That effect is especially strong when the part-time person carries critical knowledge or owns a step the rest of the team cannot easily absorb.
Plan from the actual sprint, not a generic average
Historical averages become less reliable when the shape of availability changes sprint to sprint.
A part-time contributor who is usually available two mornings a week may not be available in the same pattern next sprint. That is why the upcoming sprint's actual schedule matters more than a rough memory of how things usually feel.
What usually goes wrong
Teams often get this wrong when they mark part-time people as "half available" but do not account for fragmentation, support load, or coordination drag around that partial availability.
- Part-time contributors are counted too generously.
- Shared roles are double-booked across teams.
- Meeting overhead eats a bigger share of partial schedules.
- The sprint plan assumes smooth collaboration where the calendar says otherwise.
Where to go next
If your sprint commitments keep assuming more part-time capacity than the team really has, the capacity tool is the best next step.
That is where the team can translate partial availability into a more honest view of what the sprint can actually carry.
TL;DR
- Plan part-time team members by usable availability, not headcount.
- Partial schedules lose more capacity when meetings and context switching are counted.
- Shared specialists should shape sprint commitment early.
- Part-time planning gets better when the team works from usable sprint room instead of nominal headcount.