Engineering Capacity Planning - Scrums.com Docs

Plan from measured capacity

Engineering capacity planning compares the capacity your teams can realistically use with the work already committed to your roadmap. Scrums.com combines project and delivery signals so you can see where capacity goes and where commitments are at risk.

Allocation classes

Classify work consistently across:

Feature development
Maintenance
Technical debt
Support and escalations
Unplanned work

You can then review allocation by team, project, initiative, or client.

Commitment signals

Signal	Meaning
Sprint completion	Planned work completed within the sprint
Scope movement	Work added after the sprint starts
Commitment ratio	Committed work compared with completed work
Forecast status	Whether an initiative remains within its forecast window

Close a capacity gap

First identify the constraint. Then choose the response that fits it:

Add an engineer for a durable skill or capacity gap.
Deploy a team for a whole delivery unit.
Define a managed scope for a bounded outcome.
Use an agent for repetitive, well-specified work.
Add infrastructure when environments or pipelines are the constraint.

Measure the same signals after the deployment to confirm whether it resolved the constraint.

Last modified on September 15, 2026