Agile

Kent Beck's argument is that the practices that make software reliable — pair programming, test-first, continuous integration, small releases, collective code ownership — are not independent techniques. They reinforce ea…

Four values and twelve principles drafted in February 2001 by seventeen consultants who disagreed about almost everything except the importance of shipping working software. The Manifesto is short, quotable and twenty-fi…

Larman and Basili walk through forty years of software projects that used iterative and incremental development — from Mercury and the early space programme through shuttle avionics to the first large commercial systems…

The Poppendiecks translate Toyota's manufacturing principles into software terms: eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible, respect people, see the whole. The translation…

Coplien's work on organisational patterns predates most of the agile movement and is in many ways deeper than the movement it foreshadowed. The piece collects patterns observed in high-performing software organisations —…

Anderson's central claim is subtle: you do not adopt Kanban, you discover it by making your current work visible. Start where you are, make WIP limits explicit, manage flow — and the process improves itself. The virtue o…

A comparative textbook that treats Scrum, XP, Lean and Kanban as related but distinct practices, with careful attention to what each one is good at and what it is not. The book is less polemical than most agile writing,…

Burnett's argument is the one many product directors have been quietly thinking but struggle to say out loud: the word "agile" has been consumed by the industry it was meant to correct, and what is sold today under its n…