chapter one

1 Why Lean, why now?

 

This chapter covers

  • Why modern software systems outpace traditional delivery-model assumptions
  • 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 are no faster, more predictable, or less painful. Toolchains and AI code generation have expanded rapidly, yet lead times remain long, defects persist, and developers face more process friction and rework. The problem isn’t talent or effort. It’s that our systems are poorly understood and rarely designed for this era.

1.1 Persistent friction in modern coding

1.1.1 What does “Lean” mean for code?

1.1.2 Making the delivery system visible

1.1.3 Scenario 1: Refactoring with an AI agent

1.1.4 Scenario 2: Long-lived context windows and dead code paths

1.1.5 Scenario 3: The illusion of completion

1.2 From idea to delivered feature in a modern system

1.2.1 Loop 1: The work loop

1.2.2 Loop 2: The Lean lens

1.2.3 Principles in action

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

1.2.5 A flexible, holistic model

1.3 Your lean journey ahead

1.4 Summary