Changing how an organisation funds, structures and governs work, once single team practice is no longer the constraint.
A team can run good Scrum inside an organisation that makes good Scrum beside the point, which is why transformation reading is a different shelf from delivery reading. These cover funding, governance, organisational design and the change work itself, ordered from the diagnosis through to the mechanics of running an adoption. The list suits agile coaches, transformation leads, and programme and portfolio managers responsible for more than one team.
Patterns paired with the antipattern each one replaces, drawn from banking and other regulated industries. That pairing makes the book usable as a diagnostic when a change programme has stalled and nobody can say why.
The funding argument, which is where most transformations quietly come apart. The Flow Framework gives you flow items and flow metrics that connect delivery activity to business results a finance function recognises.
Denning on the management model surrounding the teams, framed as three laws covering the small team, the customer and the network. Written for the executive conversation rather than the team one.
Cagan on moving an existing organisation to a product operating model, with the objections each of the four dimensions runs into. The assessment questions are the fastest way to locate where you actually stand today.
Organisational design as the lever, using four team types and three interaction modes. The reverse Conway argument is the one that changes how leaders think about a reorganisation before they announce it.
Cohn's ADAPT model, plus the practical choices about piloting, spreading practice across teams and the resistance each stage meets. Still the most complete treatment of adoption mechanics.
Larman and Vodde on thinking tools rather than practices, including queueing theory, systems thinking and organisational design for many teams on one product. Dense, and the chapters on local optimisation are the ones people return to.
Larson treats organisational design as a systems problem, in short essays you can read when a specific problem lands. Particularly good on team sizing and on running a technical migration to completion.
Case studies from manufacturing, banking, aerospace and government. Useful evidence to have to hand when somebody argues the approach only applies to software teams.
Written by the authors of Scrum for managers and executives rather than for teams, covering funding, governance and risk under an empirical approach. Short enough to hand to a sponsor and expect it back read.