chapter one

1 Why Lean, why now?

 

This chapter covers

  • Why modern software moves faster than the delivery models built to manage it
  • How AI-assisted development alters, not solves, core delivery constraints
  • Lean: a developer-centric framework for value, waste, and flow
  • Connecting intent to running software in complex systems

Modern software teams ship more code than ever, yet outcomes aren't delivered faster, more predictably, or less painfully. Toolchains and AI code generation have expanded rapidly, yet lead times remain long, defects persist, and developers still face significant process friction and rework. The problem is not talent or effort. It is that our delivery systems are poorly understood and rarely designed for this era. Lean thinking offers a practical, developer-focused response: identify what creates value for users, expose waste (any effort that consumes time, attention, or resources without creating value), and improve the flow of work across design, coding, testing, and deployment.

1.1 Persistent friction in modern coding

1.2 What does “Lean” mean for code?

1.3 Making the delivery system visible

1.3.1 Refactoring with an AI agent

1.3.2 Long-lived context windows and dead code paths

1.3.3 The illusion of completion

1.4 From idea to delivered feature in a modern system

1.4.1 Loop 1: The work loop

1.4.2 Loop 2: The Lean lens

1.4.3 Putting it all together: Principles as cross-cutting forces

1.4.4 A flexible, holistic model

1.5 Your Lean journey ahead

1.6 Summary