liveBook · Manning

Capacity

As explained in Build High Value Software Systems

The amount of work a delivery system or team can handle within a given period.

Planning as if every week offers five full days for tickets ignores meetings, reviews, mentoring, and other commitments. Capacity is the time actually available for ticket work after those commitments are accounted for. section 14.4.1

Make weekly capacity visible and plan around it:

  • Count non-ticket commitments before estimating ticket work; eight hours of commitments can leave roughly three days for tickets. section 14.4.1
  • Share commitments and their beneficiaries with the team so everyone can plan against the same capacity. section 14.4.1
  • Pair a ticket limit with visible, planned commitments; limiting tickets alone does not protect deep work from unpredictable interruptions. section 14.4.1
Table 14.3 WIP impact on weekly throughput
Metric
Developer A: No WIP limit
Developer B: Ticket limit only
Developer C: Holistic WIP
Tickets in progress
4
1
1
Non-ticket commitments
Untracked, scattered
Untracked, scattered
Visible, planned into the week
Planned deep work hours
40 (assumes full week)
40 (assumes full week)
24 (accounts for 16h of meetings, reviews, mentoring)
Actual deep work hours
~15 (rest lost to switching)
~25 (less switching, but meetings still fragment)
~22 (fewer hours planned, more of them protected)
Context switches/week
12-15
4-6
0-2
Tickets completed
0-1
2-3
3-4
Non-ticket quality
Shallow, rushed between ticket switches
Attended but unplanned, displaces deep work unpredictably
Prepared, scheduled, and given real attention

Compare ticket limits alone with holistic planning: the table tracks planned and actual deep-work hours, context switches, tickets completed, and non-ticket work quality. section 14.4.1

How Build High Value Software Systems covers it

How deep it goes
Explains capacity through weekly planning and a throughput comparison, without giving a forecasting formula.
Examples
Compares three developers’ ticket limits, planned and actual deep-work hours, context switches, and completed tickets.
What you can do after
Practice planning ticket capacity around visible commitments and sharing the resulting estimate with the team.
How it connects
Connects capacity with work-in-progress limits, deep work, context switching, and non-ticket commitments.

Also explained in

Compare how 8 books explain capacity →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.