Lean, Agile and Iterative

This paper covers the agile and lean reaction to plan-driven delivery — delivering complex, uncertain work through short iterations, flow and feedback rather than a fixed up-front plan. Kent Beck brought disciplined engineering and continuous delivery through Extreme Programming; Sutherland and Schwaber gave agile its dominant empirical framework in Scrum; Anderson applied lean flow to knowledge work through Kanban; Reinertsen supplied the economic and queueing theory underneath all of it.

Where the traditional, plan-driven tradition specifies work in advance, this one inspects and adapts: transparency, short timeboxed sprints, and work-in-progress limits replace the illusion of a perfect plan, with Reinertsen's cost-of-delay economics giving the prioritisation logic that keeps flow-based methods rigorous rather than merely energetic.

For the operator, the lesson is to manage flow and feedback rather than plans when the work is uncertain and complex, and to prioritise by cost of delay rather than instinct. The next paper in the series scales the same questions up to programs, portfolios and megaprojects.