liveBook · Manning

Chapter 1: Why Lean, why now?

What you will learn in chapter 1 of Build High Value Software Systems

The chapter introduction explains why more code and faster tools do not necessarily improve delivery, and presents Lean as a developer-focused way to improve the whole system of work.

After this chapter you will be able to

Section by section

Introduction

The chapter introduction explains why more code and faster tools do not necessarily improve delivery, and presents Lean as a developer-focused way to improve the whole system of work.

Key terms: lead times, rework, systemic slowdowns, AI coding assistants, Lean thinking, value, waste, flow, delivery system, end-to-end delivery system

1.1 Persistent friction in modern coding

This section explains why faster code creation can coexist with persistent delivery friction, and why teams need to examine the whole delivery system.

Key terms: software development lifecycle (SDLC), constraints, AI-assisted development, feedback loops, handoff, persistent friction, human judgment moves upstream, standards, rework, invisible queues

1.1.1 What does “Lean” mean for code?

This section translates five Lean manufacturing principles into software development, shifting attention from code output to how reliably a delivery system creates lasting user value.

Key terms: value, capability, enduring value, value stream, SDLC, work queues, flow, decision bottlenecks, confidence gaps, pull

1.1.2 Making the delivery system visible

The section frames software delivery problems as breakdowns in flow that Lean principles can make visible and help prevent or mitigate.

Key terms: implicit constraints, work in progress, full value stream, feedback loops

1.1.3 Scenario 1: Refactoring with an AI agent

An AI refactoring scenario shows how faster code changes can create rework when important constraints are left implicit and feedback arrives only in production.

Key terms: AI agent, architectural assumptions, domain boundaries, operational constraints, intent, Lean perspective, architectural fitness functions, decision records, load testing, definition of done

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

This section shows how an extended AI-assisted coding session can leave dead code behind and frames the problem as unfinished work that needs clearer completion criteria.

Key terms: AI-assisted development session, dead code, coherence, work-in-progress (WIP), completion criteria, done, cognitive overhead

1.1.5 Scenario 3: The illusion of completion

This section shows how an AI-generated feature can appear finished while hiding production costs, and argues for a broader definition of value and done.

Key terms: definition of value, full value stream, production readiness, technical debt, feedback, responsibility, delivery system

1.2 From idea to delivered feature in a modern system

This section presents software delivery as a feedback loop and shows how its stages and a Lean lens help diagnose delays as system problems.

Key terms: software delivery system, intent, execution, validation, learning, AI, alignment, ownership, delivery loop, bottleneck

1.2.1 Loop 1: The work loop

The section traces a feature through the software-delivery work loop and shows why faster code generation alone does not resolve delivery delays, defects, or rework.

Key terms: work loop, Software Development Lifecycle (SDLC), Intent, Code, Build/Test, Review, bottlenecks, alignment, validation, feedback

1.2.2 Loop 2: The Lean lens

The section applies five Lean questions to a troubled feature delivery, using them to locate waste in the system rather than blame individuals.

Key terms: Lean lens, engineering judgment, systemic improvement, Value, Flow, Pull, waste, Quality, Learning, defect in intent

1.2.3 Principles in action

The section shows how a team turns Lean principles into concrete work practices and system enablers that make those practices consistent.

Key terms: system enablers, work loop, waste, value and pull, acceptance criteria, PR template, entry criteria, flow, review queue, PR size

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

The section maps five Lean interventions onto the software delivery loop and shows how making constraints explicit, catching problems earlier, and learning from incidents improved delivery.

Key terms: Value & Pull, entry criteria, Intent → Code, Quality, event sourcing pattern, architectural constraints, Code → Build & Test, Flow, production-like data volumes, legacy schemas

1.2.5 A flexible, holistic model

The section shows how five Lean principles apply across the entire delivery loop, giving teams a system-level way to question delays, readiness, quality, and value.

Key terms: Lean principles, delivery loop, holistic system, Value, lasting user capability, local optimization, Flow, review queues, feedback, waste

1.3 Your lean journey ahead

The section frames Lean as a way to observe complex software delivery systems and improve them steadily while respecting the people doing the work.

Key terms: Lean, complexity, value, observe, constraints, waste, small changes, attention, judgment, learning

1.4 Summary

Where this is used later

Concepts explained in this chapter

Chapter 2: Value and waste in software →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.