Planning when the scope is deliberately open, measuring progress without a percentage complete, working with a fixed date, handling dependencies on teams that work differently, and technical debt.

For readers on a team that has adopted agile practices and found that the difficult parts did not go away. This level is about the parts nobody warns you about.

The level leaves you able to plan realistically inside an agile cycle, report progress to someone who wants a date, and keep a team delivering when part of the work depends on people outside it.

Coordinating several teams without recreating a command structure, scaling patterns and their costs, funding work that has no fixed scope, and keeping decisions close to the people doing the work.

Written for people running agile work at a size where one team is no longer the unit. Coordination costs start to dominate.

You come away able to coordinate work across several teams without adding a layer of control, judge which scaling pattern suits a situation, and keep autonomy intact as the work grows.

Why agile adoptions stall, the structural changes that have to accompany them, where these approaches genuinely do not fit, and how to tell a culture change from a vocabulary change.

The deepest level, for readers asked whether an organisation should work this way at all, and what it would cost to mean it.

You can judge whether an organisation is capable of the change it is describing, name the structural obstacles honestly, and argue against adopting these methods where they do not fit.