Commitment is the future effort tied to software work or artifacts: the harder something is to understand, change, replace, or delete, the more it commits the team. Generated code that must be reviewed, debugged, and maintained carries more commitment than an artifact that can be cheaply regenerated or discarded. section 3.2.2
Commitments also include non-ticket work that uses time otherwise available for focused work. Make that work visible and include it in capacity planning; otherwise, ticket plans can assume time that is not actually available. section 14.4.1
Two kinds of commitment
A disposable generated artifact can be replaced cheaply, keeping its commitment low. A week with eight hours reserved for reviews, mentoring, or knowledge sharing has less ticket capacity than a five-day week; make those hours visible when planning. section 3.2.2 section 14.4.1
Figure 3.4 Low effort + low commitment = Lean AI usage.
Use the figure’s low-effort, low-commitment lens to assess whether an AI-assisted task reduces work without adding lasting maintenance cost. section 3.2.2
