liveBook · Manning

Chapter 2: Value and waste in software

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

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.

After this chapter you will be able to

What it builds on

Section by section

Introduction

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.

Key terms: creating value, enabling value, consuming capacity, activity, outcomes, clarity, effort, flow, risk, learning

2.1 Seeing value before improving flow

This section uses a delayed bug fix to show why improving software flow starts with identifying customer value and the waste hidden inside apparently responsible work.

Key terms: value, waste, waiting, handoffs, rework, customer’s perspective, internal ones, indirect, non-feature work, necessary

2.2 Types of value in software

This section shows why identifying value in software requires asking who a piece of work serves and using three overlapping lenses to articulate why it matters.

Key terms: customer, internal, user value, business value, technical value

2.2.1 User value

Defines user value as a concrete improvement in users’ experience or capability, including improvements that do not add features.

Key terms: user value, reliability, correctness, predictability, user task, UX

2.2.2 Business value

Defines business value, explains why its less visible forms are often deferred, and connects it to user value.

Key terms: business value, revenue generation, cost reduction, regulatory compliance, risk management, short-term delivery pressure, support ticket load, user value, churn, technical debt

2.2.3 Technical value

This section defines technical value and explains why internal improvements must be justified by the future value they enable.

Key terms: technical value, internal qualities, future value, friction, risk, delay, overengineering

2.2.4 Value is contextual, not absolute

This section explains why software work has no fixed value: its worth depends on context, the outcomes it enables, and who benefits.

Key terms: value, waste, risk profile, system maturity, chain of enablement, technical value, business value, user value, Lean, intent

2.3 Value-adding versus non-value-adding work

This section introduces a customer-value test for distinguishing value-adding work from non-value-adding work, while explaining why necessary supporting work and context complicate that distinction.

Key terms: value-adding work (VA), non-value-adding work (NVA), customer-defined value, necessary, waste, diagnostic tool, rigid taxonomy, context, risk

2.3.1 Value-adding work (VA)

Defines value-adding software work by the customer-relevant outcome it creates, rather than the effort or sophistication involved.

Key terms: value-adding work, outcome, customer

2.3.2 Non-value-adding work (NVA)

Defines non-value-adding work and explains why making it visible helps improve the system without blaming the people doing it.

Key terms: non-value-adding work, NVA, customer value, Lean

2.3.3 Necessary vs unnecessary work

This section distinguishes necessary from unnecessary non-value-adding work so teams do not remove safeguards while trying to reduce waste.

Key terms: non-value-adding, necessary non-value-adding (NNVA) work, unnecessary non-value-adding work (waste)

2.3.4 Necessary non-value-adding work (NNVA)

This section explains why necessary non-value-adding work protects software delivery and how to keep that protection proportionate and efficient.

Key terms: necessary non-value-adding work, NNVA, NNVA work, risk downstream, stability, trust, normal development flow, automation, manual toil

2.3.5 Unnecessary non-value-adding work

This section explains how unnecessary non-value-adding work hides in routine software practices and why Lean treats it as a system-level problem rather than an individual failure.

Key terms: unnecessary non-value-adding work, value, risk, waste, patterns of friction, flow of value, lead time, capacity, locally rational, system level

2.3.6 Using VA/NVA as a thinking aid

This section presents VA/NVA classifications as a context-sensitive aid for questioning why software work exists and what outcome it enables.

Key terms: value-adding, non-value-adding, context, maturity, risk

2.4 The eight wastes in software development

Introduces the eight wastes as a way to spot hidden, system-created friction in software work and shows how that friction can prevent a feature from delivering value.

Key terms: eight wastes, TIMWOODS, diagnostic lens, unnecessary non-value-adding work, technical value, business value, user value, enablement chain, Order History

2.4.1 Transport

This section explains transport waste as unnecessary movement or translation of information, its cumulative costs, and how to distinguish it from necessary boundaries.

Key terms: transport, transport waste, mapping, handoff, boundaries, translations

2.4.2 Inventory

Defines inventory waste in software and explains how unfinished work and decisions create ongoing maintenance costs.

Key terms: inventory, work in progress, surface area, feature flags, code paths, unfinished decisions

2.4.3 Motion

Defines motion waste in software and shows how missing context in systems makes engineers spend attention navigating and reconstructing meaning instead of solving problems.

Key terms: motion, transport, cognitive effort, low-context systems, intent, tribal knowledge, motion waste

2.4.4 Waiting

The section explains how delayed feedback creates waiting waste, often hides it behind other work, and increases lead time and rework.

Key terms: waiting, delayed feedback, lead time, parallel work, rework, full system integration, external services, fast feedback unit boundaries, test coverage

2.4.5 Overproduction

This section explains how building software before there is a clear need creates hidden maintenance work, even when the code is well designed.

Key terms: overproduction, complexity, AI-assisted development, generality, abstraction, future-proof, failure of timing

2.4.6 Overprocessing

This section explains overprocessing as complexity beyond current customer needs and shows how to question whether that complexity is justified.

Key terms: overprocessing, overproduction, current customer needs, configuration, indirection, variability, setup costs

2.4.7 Defects

This section shows how defects waste effort through both obvious failures and subtle errors, as well as through the workarounds that accumulate around them.

Key terms: defects, losses of intent, happy-path tests, incorrect assumptions, workarounds, known failure modes, underlying causes

2.4.8 Skills (unused talent)

This section explains how skilled engineers’ judgment becomes wasted when they must compensate for system deficiencies rather than solve meaningful problems.

Key terms: Skills (unused talent), underutilized talent, judgment, waiting, defects, overprocessing, inventory, experienced judgment

2.4.9 From seeing waste to improving the system

This section explains why workarounds can hide systemic waste and introduces Gemba and Kaizen as ways to ground improvement in observed work.

Key terms: waste, workarounds, friction, Gemba, Kaizen, Toyota Production System

2.5 Gemba and Kaizen in software development

This section explains how observing real software work at the Gemba and making small, continuous Kaizen changes help teams address recurring waste.

Key terms: Gemba, observation, Kaizen, continuous improvement, system, CI pipelines, feedback delays, nondeterminism, flow

2.6 Exercise: Audit your last pull request for waste

This section gives readers a reflective method for spotting waste in pull requests and identifying small system changes that might reduce it.

Key terms: pull request, VA, NNVA, Waste, system constraint, friction

2.7 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 1: Why Lean, why now? Chapter 3: AI as a partner and problem →

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.