1 Why Lean, why now?

Modern software teams are shipping more code than ever, but delivery is still slow, unpredictable, and frustrating because the real problem is systemic, not a lack of talent or effort. Cloud platforms, CI/CD pipelines, distributed systems, and AI-assisted coding have made it easier to produce code, but they have also shifted the bottlenecks to understanding, validation, integration, deployment, and maintenance. In this environment, extra automation can increase throughput without improving outcomes if the delivery system itself is not designed to handle the work flowing through it.

Lean is presented as a practical, developer-centered way to improve that system by focusing on value, waste, flow, pull, and continuous improvement. Instead of treating Lean as a management style or a checklist, the chapter frames it as a way to make work visible, reduce rework, expose hidden queues, and encode standards earlier so that intent is preserved as code moves toward production. The text emphasizes that AI does not remove delivery constraints; it can actually amplify waste unless teams deliberately shape standards, feedback loops, and readiness signals.

To make the ideas concrete, the chapter uses scenarios where features take far longer than expected because requirements are unclear, architectural constraints are implicit, test environments are unrealistic, or production performance is not validated soon enough. These examples are used to build a simple mental model of software delivery as a continuous loop from intent to code to build and test to run and back again through feedback. Lean thinking then becomes a set of questions for diagnosing where work stalls and a set of practices for improving the system so that value reaches users faster, with less friction, and with better learning over time.