liveBook · Manning

What you will learn in Build High Value Software Systems

How to eliminate waste across the software delivery lifecycle

by Leigh Griffin · Manning Early Access Program (MEAP)

Chapter by chapter

Chapter 1: Why Lean, why now?

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.

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

What you learn in chapter 1 →

Chapter 2: Value and waste in software

The chapter introduction argues that improving software delivery starts with distinguishing work that creates value, enables value, or consumes capacity, rather than simply increasing effort.

2.1 Seeing value before improving flow · 2.2 Types of value in software · 2.2.1 User value · 2.2.2 Business value · 2.2.3 Technical value · 2.2.4 Value is contextual, not absolute · 2.3 Value-adding versus non-value-adding work · 2.3.1 Value-adding work (VA) · 2.3.2 Non-value-adding work (NVA) · 2.3.3 Necessary vs unnecessary work · 2.3.4 Necessary non-value-adding work (NNVA) · 2.3.5 Unnecessary non-value-adding work · 2.3.6 Using VA/NVA as a thinking aid · 2.4 The eight wastes in software development · 2.4.1 Transport · 2.4.2 Inventory · 2.4.3 Motion · 2.4.4 Waiting · 2.4.5 Overproduction · 2.4.6 Overprocessing · 2.4.7 Defects · 2.4.8 Skills (unused talent) · 2.4.9 From seeing waste to improving the system · 2.5 Gemba and Kaizen in software development · 2.6 Exercise: Audit your last pull request for waste · 2.7 Summary

What you learn in chapter 2 →

Chapter 3: AI as a partner and problem

The chapter introduction shows how AI can speed up useful work or quietly introduce unchosen business rules, and frames Lean thinking as a way to distinguish the two.

3.1 Keeping the human above the loop · 3.1.1 The problem with being in the loop · 3.1.2 Positioning the human above the loop · 3.1.3 What this means in practice · 3.1.4 From collaborator to power tool · 3.2 How AI helps you stay lean · 3.2.1 The API service example · 3.2.2 The Lean principle at work · 3.3 Where AI creates waste · 3.3.1 The unconstrained prompt · 3.3.2 Breaking down the waste · 3.4 Establishing your AI standard work · 3.4.1 What the API service team established · 3.4.2 Making AI boundaries explicit · 3.4.3 Standard work as flow protection · 3.5 Exercise: Compare handwritten vs AI-generated code · 3.6 Summary

What you learn in chapter 3 →

Chapter 4: Writing Lean code

The introduction frames Lean coding as preventing unnecessary work by deciding what code is needed and keeping it easy to understand, change, or delete.

4.1 From code to spec: The evolution of defining intent · 4.1.1 The waterfall era: Code is truth · 4.1.2 Evolving to shift the source of truth · 4.1.3 The AI era: Specs become explicit · 4.1.4 Spec first: Define before you build · 4.2 Design for deletion · 4.2.1 Making code deletable · 4.2.2 Designing for intervention: Enabling the software Andon · 4.3 Managing dependencies and their hidden costs · 4.3.1 The value of dependencies · 4.3.2 Surface area · 4.3.3 AI as a dependency · 4.3.4 AI as a dependency generator · 4.4 Standard work for coding · 4.4.1 To spec or not? · 4.4.2 Writing code · 4.4.3 The code review · 4.5 Exercise: From vibe coding to Lean coding · 4.5.1 Start with vibe coding · 4.5.2 Write the spec · 4.5.3 Compare and contrast · 4.5.4 Delete everything not in the spec · 4.5.5 Reflect · 4.6 Summary

What you learn in chapter 4 →

Chapter 5: Testing as waste prevention

The chapter introduction shows how tests can either prevent rework or create waste, depending on the risks they protect and the costs they impose.

5.1 Value-add versus wasteful testing · 5.2 Tests as design constraints · 5.3 Structuring test layers around risk · 5.4 Identifying flaky tests as flow-blocking defects · 5.4.1 When signals lose meaning · 5.4.2 Flow metrics · 5.5 Inflating coverage without protecting value · 5.6 Deciding what not to automate · 5.6.1 Waste elimination and creation · 5.6.2 Automation as a value stream · 5.7 Coverage metrics: Expose risk, not inflate confidence · 5.8 Exercise: Expose and reduce one source of testing waste · 5.9 Summary

What you learn in chapter 5 →

Chapter 6: Flow in your development cycle

The introduction frames software delivery as a value stream from idea to production and explains why unfinished work and delays between steps matter more than visible activity.

6.1 Understanding flow, from idea to production · 6.1.1 Multiple value streams · 6.1.2 The metrics value stream · 6.1.3 The tip of the iceberg · 6.2 Reducing batch sizes for faster feedback · 6.3 Limiting work in progress · 6.4 Identifying and avoiding bottlenecks · 6.4.1 Elevating the constraint · 6.4.2 Designing the future value stream · 6.5 CI/CD: Flow enabler or disruptor? · 6.5.1 CI/CD as flow enabler · 6.5.2 CI/CD as flow disruptor · 6.5.3 A balanced scorecard for flow-centric CI/CD · 6.5.4 Lean release strategies: Designing flow beyond deployment · 6.6 Exercise: Trace one feature and remove one delay · 6.7 Summary

What you learn in chapter 6 →

Chapter 7: Taming legacy code

The introduction defines legacy code by how safely it can be changed and explains why it disrupts development flow.

7.1 Understanding legacy code through a Lean lens · 7.1.1 Two traps · 7.2 Identifying and prioritizing waste in legacy code · 7.2.1 Prioritizing waste by impact · 7.3 Lean design principles for legacy code · 7.3.1 YAGNI as a Lean design principle · 7.3.2 Lean perspective on design patterns · 7.4 Attacking a legacy codebase systematically · 7.4.1 Technical debt · 7.5 Exercise: Tame one legacy module this release · 7.6 Summary

What you learn in chapter 7 →

Chapter 8: Root cause thinking for developers

The introduction uses a recurring payment-service failure to show why developers should trace evidence to a changeable root cause instead of repeatedly restoring service with temporary fixes.

8.1 Going beyond symptoms to the root cause · 8.2 Lean problem-solving tools and techniques · 8.2.1 The 5 whys · 8.2.2 Fishbone diagrams · 8.2.3 Pareto analysis · 8.2.4 Is/Is not · 8.2.5 Combining them: Root cause analysis · 8.3 Debugging at the gemba · 8.4 When AI introduces non-RCA fixes · 8.5 Countermeasures, not quick fixes · 8.6 A3 reports: Structured, blameless problem solving · 8.7 RCA beyond your value stream · 8.8 Exercise: Write an A3 report for a production issue · 8.9 Summary

What you learn in chapter 8 →

Chapter 9: Measuring what matters

The chapter introduction frames metrics as a way to expose hidden system problems and judge whether measured improvement is real.

9.1 Why measure? Making problems visible · 9.1.1 Measurement for learning versus ranking · 9.1.2 The optimization trap · 9.2 Lean metrics for developers · 9.2.1 Lead time · 9.2.2 Cycle time · 9.2.3 Activity time · 9.2.4 Beyond the fundamentals · 9.3 Avoiding vanity metrics and metric gamification · 9.4 Visual dashboards for continuous improvement · 9.4.1 From flow signals to flow dashboards · 9.4.2 Making it work in practice · 9.5 Exercise: Calculate your current lead time · 9.6 Summary

What you learn in chapter 9 →

Chapter 10: Kaizen: Continuous improvement

The introduction presents Kaizen as a sustained habit of making small, measured improvements to the development system, rather than occasionally cleaning up code.

10.1 What Kaizen actually means · 10.1.1 Small · 10.1.2 Continuous · 10.1.3 By the people who do the work · 10.1.4 From mindset to method · 10.2 Kaizen versus refactoring · 10.3 Retrospectives as structured Kaizen · 10.3.1 Why retrospectives fail · 10.4 A3 as a communication API for improvements · 10.5 Developer-led Kaizen · 10.5.1 Personal practices · 10.5.2 Anchoring your practices · 10.6 Exercise: Run a personal Kaizen event · 10.7 Summary

What you learn in chapter 10 →

Chapter 11: Architectures that flow

The introduction shows why architecture must be examined as a value stream, even when code and development processes are working well.

11.1 Set-based design · 11.2 The last responsible moment · 11.2.1 Decisions that can wait · 11.2.2 Decisions that cannot wait · 11.2.3 Tracking decisions · 11.3 Value stream mapping at the system level · 11.4 Finding the system bottleneck · 11.5 Pull versus push · 11.5.1 Backpressure: The safety valve · 11.6 Takt time and system rhythm · 11.6.1 Calculating takt time · 11.7 Building quality in · 11.8 A system that flows · 11.9 Exercise: Mapping, measuring, and improving your architecture · 11.10 Summary

What you learn in chapter 11 →

Chapter 12: Lean operations and production

A deployment scenario shows why Lean operations must look beyond successful delivery and green dashboards to how the system actually runs.

12.1 Shifting from development to operations mindset · 12.1.1 Development velocity versus operational stability · 12.2 Gemba in production · 12.2.1 The silent degradation pattern · 12.3 Andon for production systems · 12.3.1 The cost of not stopping · 12.3.2 Pulling the cord · 12.3.3 Three levels of andon · 12.4 Standard work for operations and incident response · 12.5 Mura, Muri, Muda · 12.5.1 Mura: The unevenness that causes outages · 12.5.2 Muri: The overburden that breaks things · 12.5.3 Muda: Capturing operational waste · 12.6 Production Kaizen · 12.6.1 Post-incident reviews as kaizen triggers · 12.7 Exercise: Audit your production system through the Lean operations lens · 12.8 Summary

What you learn in chapter 12 →

Chapter 13: Lean team culture

A failed order-routing fix shows how knowledge silos can stop delivery and why respect for people is a practical requirement for Lean improvement.

13.1 Respect for people as engineering practice · 13.1.1 What respect looks like in code · 13.2 Respect in process: Building the conditions for honesty · 13.3 Autonomy, mastery, and purpose · 13.4 Code ownership models · 13.4.1 The silo trap · 13.4.2 Moving toward collective ownership · 13.4.3 Quality as a team responsibility · 13.5 Lean onboarding · 13.6 AI as a pairing partner · 13.6.1 What AI pairing does not replace · 13.7 Building problem solvers, not order takers · 13.7.1 Reversing the pattern · 13.7.2 Sustaining and scaling the problem-solving habit · 13.8 Exercise: Assess your team's Lean maturity · 13.9 Summary

What you learn in chapter 13 →

Chapter 14: Personal Lean: Building habits

The chapter introduction applies Lean thinking to personal work habits, contrasting busy but fragmented days with deliberate, measurable improvement.

14.1 Your cognitive value and the eighth waste · 14.2 Personal standard work · 14.2.1 Building checklists from failures · 14.3 Learning loops and skill development · 14.3.1 Learning from patterns · 14.3.2 A regular cadence · 14.4 Managing your personal WIP and flow · 14.4.1 Holistic WIP limits · 14.4.2 Flow and mindset · 14.5 Staying Lean as AI evolves · 14.5.1 AI and the T-shaped developer · 14.6 Exercise: Create your personal standard work guide · 14.7 Summary

What you learn in chapter 14 →

Chapter 15: Leading Lean change

The introduction frames Lean change as a learnable, people-centered skill and proposes starting with small, measured improvements that developers share with their teams.

15.1 Influence without authority · 15.1.1 The pattern: Act, measure, share · 15.2 Micro coaching · 15.2.1 Micro coaching framework · 15.2.2 From micro coaching to coaching kata · 15.3 Demonstrating value through small wins · 15.4 Scaling improvements across teams · 15.5 Handling resistance to change · 15.5.1 We have always done it this way · 15.6 Building a culture of continuous learning · 15.7 The change agent’s toolkit · 15.8 Exercise: Plan your first team Kaizen event · 15.9 Summary

What you learn in chapter 15 →

Concepts explained in this book

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.