Capacity and Commitment Distinction
In Agile project management, understanding the distinction between capacity and commitment ensures realistic planning and sustainable team performance.
Capacity and Commitment Distinction is the conceptual separation between how much work a team is realistically able to perform in a given period, its capacity, and how much work the team has agreed to deliver, its commitment. Although the two figures are closely related and a healthy commitment should never exceed available capacity, conflating them leads to planning errors, since capacity is a measurable constraint while commitment is a negotiated decision made within that constraint.
Core Concept
Capacity as a Ceiling, Commitment as a Choice
Capacity represents the maximum amount of work a team could realistically complete, calculated from availability, overhead, and historical performance. Commitment is the specific, smaller or equal quantity of work the team formally agrees to deliver within that capacity, chosen deliberately rather than automatically set to match the ceiling.
Why the Two Are Not Interchangeable
Treating capacity and commitment as identical implies a team should always commit to exactly its full calculated capacity every iteration. In practice, teams often deliberately commit to less than full capacity, preserving a buffer, or occasionally commit to slightly more when confidence in overachievement is unusually high, making the relationship between the two figures a matter of judgment rather than automatic equivalence.
Capacity in Detail
A Measured, Not Chosen, Quantity
Capacity is derived from objective or semi-objective inputs, such as individual availability, focus factor, and historical throughput. It describes what is realistically possible given current constraints, independent of what the team decides to promise.
Capacity Fluctuates With Circumstance
Because its inputs change from sprint to sprint, capacity is inherently variable, requiring the reassessment practices described in capacity reassessment to remain accurate as a planning input.
Commitment in Detail
A Negotiated, Deliberate Decision
Commitment is arrived at through discussion among the team, informed by capacity but also shaped by confidence levels, the presence or absence of a protective buffer, and strategic considerations such as an upcoming deadline or a desire to demonstrate reliability to stakeholders.
Commitment as a Social Contract
Once made, a commitment functions as an agreement the team holds itself accountable to, distinct from capacity, which carries no inherent promise. This social and motivational dimension is part of why commitment matters as a concept separate from a purely mechanical capacity ceiling.
Why the Distinction Matters
Prevents Automatic Overcommitment
If a team treats its full calculated capacity as an automatic commitment, any inaccuracy in the capacity calculation, or any unforeseen variance, directly produces a missed commitment. Deliberately choosing a commitment somewhat below capacity absorbs this risk.
Enables Deliberate Trade-offs
Recognizing capacity and commitment as distinct allows a team to make conscious tradeoffs, such as accepting a lower commitment during a sprint following a difficult release, without needing to justify the choice as a change in underlying capacity.
Clarifies Accountability
When a sprint underdelivers, distinguishing capacity from commitment helps identify whether the root cause was a capacity miscalculation, an overly aggressive commitment decision, or execution issues unrelated to either, leading to more precise retrospective analysis.
Common Confusions
Treating Historical Velocity as Automatic Commitment
Some teams mechanically commit to whatever their average historical velocity suggests as available capacity, without deliberately deciding whether that full figure is the right commitment for the specific upcoming sprint, given its particular circumstances.
Using Commitment Figures to Infer True Capacity
Observers sometimes assume a team's historical commitments reveal its true capacity, when in fact a team that has consistently under-committed relative to its actual capacity, whether deliberately or not, will show a lower apparent capacity than truly exists.
Punishing Capacity Variance as a Commitment Failure
When capacity genuinely shifts due to unforeseen circumstances, such as sudden illness, holding the team strictly to a commitment made before that shift occurred conflates a capacity change with a failure of will or effort.
Applying the Distinction in Practice
Calculate Capacity First, Decide Commitment Second
Establishing the capacity figure through objective calculation before any discussion of what to promise keeps the two steps appropriately separated and reduces the risk of anchoring commitment decisions on wishful thinking.
Document the Rationale for the Gap
When commitment is set below full calculated capacity, recording the reasoning, whether a buffer, a particular risk, or a deliberate conservative choice, makes the distinction visible and defensible to stakeholders reviewing the plan.
Review Both Figures in Retrospectives
Examining both how accurate the capacity calculation was and how appropriate the commitment decision was, as two separate questions, produces sharper retrospective insight than reviewing only whether the sprint goal was met.
Best Practices
Keep Capacity Calculation Objective
Basing capacity on measurable inputs, rather than allowing optimism about the upcoming sprint to inflate the figure, preserves capacity as a reliable ceiling against which commitment decisions can be made.
Allow Commitment to Vary Deliberately
Permitting commitment to sit below capacity when warranted, rather than treating full capacity utilization as an unquestioned default, supports more resilient and sustainable planning over time.
Communicate the Distinction to Stakeholders
Helping stakeholders understand that commitment is a chosen subset of available capacity, not identical to it, sets more accurate expectations and reduces pressure to treat every unit of capacity as an implicit promise.