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.
After this chapter you will be able to
- Three roles of work. Explain why teams need to distinguish work that creates value, enables value, or consumes capacity before trying to improve flow.
- Hidden delays in bug delivery. Trace how a bug fix requiring about eight hours of work took ten days to reach production, and explain why its delays were easy to overlook.
- Customer perspectives on value. Explain whose perspective defines value in the bug example and why some work can also serve internal customers.
- Value enabling work and waste. Distinguish work that creates value, work that enables it at a cost, and work that consumes capacity without improving outcomes.
- Customers of software work. Explain why the customer for software work is not always the product’s paying user, and describe how identifying who benefits clarifies the work’s value.
- Forms of user value. Explain how a change creates user value for people using a system, including through reliability, correctness, or predictability rather than only new features.
- Specific user task connection. Describe how to make a claim about user value concrete by identifying a frustrating user task and saying how a change will improve it.
- Forms of business value. Explain that business value is work supporting an organization's goals or constraints, whether through a visible feature or less visible cost, compliance, or risk reduction.
- Business and user value. Explain why business value and user value need not conflict, and why making both visible helps teams weigh tradeoffs rather than default to the next feature.
- Future outcomes justify technical work. Explain how to judge whether technical work creates value rather than waste by connecting it to a future outcome for users or the business.
- Context-dependent value of work. Explain why the same software activity can be valuable in one situation and wasteful in another, using the section’s automated-testing example.
- Chain of value enablement. Describe how technical, business, and user value connect, and how feedback affects which technical work is justified.
- Explicit intent for technical work. Explain how to judge a proposed piece of technical work by asking what it enables, for whom, and why now.
- Customer-defined value test. Distinguish value-adding from non-value-adding work by asking whether the work changes the product or service in a way the customer cares about, rather than judging by effort or how busy it keeps someone.
- Necessary work versus waste. Explain why some non-value-adding software work is still necessary, using the section’s examples of activities that enable or protect value.
- Customer-Felt Value Adding Work. Explain what makes software work value-adding, using the test of whether a customer would feel its loss if it were undone. Contrast a small change with a clear customer outcome against substantial work with no customer-experienced benefit.
- Non-value-adding work in software. Explain that non-value-adding work consumes time and resources without directly increasing customer value, and give examples from software development.
- System-required work without blame. Distinguish non-value-adding work from useless work, and explain why Lean makes it visible rather than blaming people for doing it.
- Necessary versus unnecessary work. Distinguish necessary non-value-adding work from unnecessary non-value-adding work, and explain why treating both as waste can lead to harmful cuts.
- Necessary protective work. Explain what necessary non-value-adding work is and give examples from software development.
- Downstream risk of removal. Justify retaining NNVA work despite its lack of direct customer-facing value.
- Proportionate low-friction safeguards. Describe how Lean evaluates and improves NNVA work without eliminating it.
- Unnecessary non-value-adding work. Explain what makes work unnecessary and non-value-adding: it consumes time and attention without creating value, protecting outcomes, or meaningfully reducing risk.
- Hidden cumulative workflow friction. Describe how ordinary routines and adaptations can conceal repeated friction, and how small instances collectively consume lead time and capacity.
- System-level view of waste. Explain why waste can feel locally rational and why naming it should make recurring patterns visible for system-level improvement rather than blame.
- Contextual VA/NVA classification. Explain why an activity’s VA/NVA classification can change and how to use the distinction when examining software work.
- Eight wastes as diagnostic lens. Explain how TIMWOODS helps identify recurring unnecessary non-value-adding work within software tasks, without treating the categories as a rigid checklist or a judgment of individuals.
- Waste disrupting the value chain. Trace how friction in the Order History example delayed delivery and weakened the connection from technical value through business value to user value.
- Transport waste and its costs. Explain how repeated reshaping, translation, or handoff of the same concept creates transport waste in software, and why a chain of individually small mappings becomes costly.
- Software inventory and its costs. Explain what counts as software inventory and why it is costly before it delivers a completed outcome.
- Permanent temporary code paths. Describe how a temporary feature-flag split becomes inventory and why the unfinished decision makes changes harder.
- Motion waste and attention. Explain what motion waste looks like in software, how it differs from transport, and why small interruptions add up.
- Missing context in artifacts. Explain how artifacts that omit intent create motion waste, using the logging example, and why the section treats this as a system-design problem.
- Hidden and compounding waiting. Explain why waiting in software development may not look like idleness and how delayed feedback affects lead time and rework.
- Validation feedback timing. Describe how validation tied to slow, high-cost dependencies creates waiting, and distinguish timely feedback from test coverage.
- Software overproduction and hidden costs. Explain what overproduction looks like in software and why it is wasteful even though it can look like progress.
- Timing of future-proof abstractions. Explain why a technically sound abstraction can still be overproduction, and describe how to question whether it is justified now.
- Overprocessing versus overproduction. Explain why work can be wasteful even when it is used, and distinguish overprocessing from overproduction.
- Visible and subtle defects. Explain that defects require rework or keep a product from meeting expectations, and that they can include plausible-looking code that fails in some contexts. Describe how AI-generated code can conceal incorrect assumptions despite passing happy-path tests.
- Workarounds as defect waste. Explain why short-term workarounds for known defects can become lasting waste when their underlying causes go unexamined. Describe the resulting friction, cognitive load, and loss of trust.
- Unused talent in software. Explain what unused talent looks like in a software team and why even important work can waste an engineer’s expertise.
- Systemic waste and hidden friction. Explain why waste can persist even when capable people are trying to do good work, and how adaptations can conceal its causes.
- Observation grounded incremental improvement. Describe how Gemba and Kaizen connect observing work where value is created with making small, continuous improvements.
- Gemba as observed work. Explain what the Gemba is in software development and why teams should observe work as it happens before deciding what to change.
- Kaizen as system improvement. Describe how Kaizen uses small, continuous changes informed by the Gemba, and explain how a team checks whether those changes help.
- Pull request work audit. Describe how to audit a recent pull request by listing its work without judgment, then classifying each item as VA, NNVA, or waste.
- System-focused waste reflection. Explain how to investigate work labeled as waste and reflect on the largest sources of friction without turning the audit into self-blame or an immediate fix.
What it builds on
- Loop 1: The work loop (chapter 1) · The work loop provides earlier context for following work through delivery.
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.
- Three roles of work: Explain why teams need to distinguish work that creates value, enables value, or consumes capacity before trying to improve flow.
Why it matters: This distinction helps a team see what its work is accomplishing before it tries to move faster. - Clarity before more effort: Explain how individually reasonable activities can collectively slow delivery, and why noticing their effects is more useful than blaming people or demanding more effort.
Why it matters: It redirects improvement from asking an already busy team to work harder toward examining the effects of its work.
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.
- Hidden delays in bug delivery: Trace how a bug fix requiring about eight hours of work took ten days to reach production, and explain why its delays were easy to overlook.
Why it matters: Looking beyond whether each step has a reason can reveal why a small fix takes so long to help a user. - Customer perspectives on value: Explain whose perspective defines value in the bug example and why some work can also serve internal customers.
Why it matters: Considering both the affected user and internal customers prevents you from mistaking every non-feature activity for waste. - Value enabling work and waste: Distinguish work that creates value, work that enables it at a cost, and work that consumes capacity without improving outcomes.
Why it matters: This distinction lets a team question costly process steps without dismissing safeguards that genuinely protect value. - Activity growth without better outcomes: Explain why visible output, including AI-generated output, can increase waste rather than improve delivery.
Why it matters: Producing more artifacts is not progress if they increase the effort needed to change and operate the system.
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.
- Customers of software work: Explain why the customer for software work is not always the product’s paying user, and describe how identifying who benefits clarifies the work’s value.
Why it matters: Naming the beneficiary makes it easier to explain why work such as a refactor or security review matters. - Overlapping lenses of value: Describe the three value lenses named here and explain why a proposed improvement needs a specific purpose rather than a generic claim of value.
Why it matters: The lenses help turn a vague request into a statement of the benefit it is meant to provide.
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.
- Forms of user value: Explain how a change creates user value for people using a system, including through reliability, correctness, or predictability rather than only new features.
Why it matters: It keeps teams from overlooking valuable improvements simply because they do not look like new features. - Specific user task connection: Describe how to make a claim about user value concrete by identifying a frustrating user task and saying how a change will improve it.
Why it matters: Naming the task and its improvement makes a proposed benefit meaningful rather than a vague aspiration.
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.
- Forms of business value: Explain that business value is work supporting an organization's goals or constraints, whether through a visible feature or less visible cost, compliance, or risk reduction.
Why it matters: This broader definition helps you recognize valuable work that does not look like a new feature. - Delayed benefits and delivery pressure: Explain why incident prevention or support-load reduction can be deprioritized when teams focus on the next release.
Why it matters: Recognizing delayed benefits makes preventive work less likely to disappear behind release deadlines. - Business and user value: Explain why business value and user value need not conflict, and why making both visible helps teams weigh tradeoffs rather than default to the next feature.
Why it matters: Considering users alongside business goals prevents fast feature delivery from masking damage to the product's long-term 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.
- Internal qualities of technical value: Describe technical value as work that improves a system’s internal qualities, using an example from the section.
Why it matters: This gives you a way to recognize technical work without assuming that every improvement is worthwhile. - Future outcomes justify technical work: Explain how to judge whether technical work creates value rather than waste by connecting it to a future outcome for users or the business.
Why it matters: It helps you explain why a technical improvement deserves time and effort.
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.
- Context-dependent value of work: Explain why the same software activity can be valuable in one situation and wasteful in another, using the section’s automated-testing example.
Why it matters: It prevents teams from treating a generally useful practice as valuable regardless of its effects in their system. - Chain of value enablement: Describe how technical, business, and user value connect, and how feedback affects which technical work is justified.
Why it matters: It makes the contribution of internal technical work to eventual user outcomes visible without assuming every technical improvement is justified. - Explicit intent for technical work: Explain how to judge a proposed piece of technical work by asking what it enables, for whom, and why now.
Why it matters: These questions help a team justify work by its present contribution rather than by its appeal in isolation.
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.
- Customer-defined value test: Distinguish value-adding from non-value-adding work by asking whether the work changes the product or service in a way the customer cares about, rather than judging by effort or how busy it keeps someone.
Why it matters: This test keeps effort from being mistaken for value. - Necessary work versus waste: Explain why some non-value-adding software work is still necessary, using the section’s examples of activities that enable or protect value.
Why it matters: The distinction prevents teams from treating safeguards as waste simply because they do not add value directly. - Context-dependent work classification: Describe why the section presents classification as a diagnostic aid rather than a fixed label for each activity.
Why it matters: It encourages examining what a particular activity accomplishes instead of assigning it a permanent label.
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.
- Customer-Felt Value Adding Work: Explain what makes software work value-adding, using the test of whether a customer would feel its loss if it were undone. Contrast a small change with a clear customer outcome against substantial work with no customer-experienced benefit.
Why it matters: This test helps you judge work by its customer impact rather than how difficult or impressive it looks.
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.
- Non-value-adding work in software: Explain that non-value-adding work consumes time and resources without directly increasing customer value, and give examples from software development.
Why it matters: Recognizing this work helps you see where effort is going without directly increasing customer value. - System-required work without blame: Distinguish non-value-adding work from useless work, and explain why Lean makes it visible rather than blaming people for doing it.
Why it matters: The point is to improve the conditions that create the work, not fault the people who must do 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.
- Necessary versus unnecessary work: Distinguish necessary non-value-adding work from unnecessary non-value-adding work, and explain why treating both as waste can lead to harmful cuts.
Why it matters: The distinction helps you remove avoidable work without cutting protections such as testing or security reviews.
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.
- Necessary protective work: Explain what necessary non-value-adding work is and give examples from software development.
Why it matters: Work can be necessary to deliver value even when customers do not directly see it. - Downstream risk of removal: Justify retaining NNVA work despite its lack of direct customer-facing value.
Why it matters: Cutting a safeguard may make delivery look faster while leaving a more costly failure for later. - Proportionate low-friction safeguards: Describe how Lean evaluates and improves NNVA work without eliminating it.
Why it matters: The aim is to preserve protection without wasting flow or engineers' judgment on repetitive toil.
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.
- Unnecessary non-value-adding work: Explain what makes work unnecessary and non-value-adding: it consumes time and attention without creating value, protecting outcomes, or meaningfully reducing risk.
Why it matters: This distinction helps you question work that feels obligatory but neither delivers value nor protects an outcome. - Hidden cumulative workflow friction: Describe how ordinary routines and adaptations can conceal repeated friction, and how small instances collectively consume lead time and capacity.
Why it matters: Looking for repeated friction reveals costs that individual workarounds can make easy to miss. - System-level view of waste: Explain why waste can feel locally rational and why naming it should make recurring patterns visible for system-level improvement rather than blame.
Why it matters: A system-level view makes it possible to address the conditions that repeatedly produce waste.
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.
- Contextual VA/NVA classification: Explain why an activity’s VA/NVA classification can change and how to use the distinction when examining software work.
Why it matters: It keeps a useful distinction from becoming a rigid judgment about work.
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.
- Eight wastes as diagnostic lens: Explain how TIMWOODS helps identify recurring unnecessary non-value-adding work within software tasks, without treating the categories as a rigid checklist or a judgment of individuals.
Why it matters: It helps you look past visible activity to find friction worth improving, rather than blaming the people doing the work. - Waste disrupting the value chain: Trace how friction in the Order History example delayed delivery and weakened the connection from technical value through business value to user value.
Why it matters: A feature can consume substantial effort without delivering its intended benefit if friction interrupts the path from implementation to use.
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.
- Transport waste and its costs: Explain how repeated reshaping, translation, or handoff of the same concept creates transport waste in software, and why a chain of individually small mappings becomes costly.
Why it matters: A series of harmless-looking mappings can consume effort and obscure where meaning was lost. - Necessary boundaries versus excess movement: Distinguish useful boundaries from transport waste, and describe the questions the section suggests for spotting unnecessary translations.
Why it matters: Questioning the purpose of each translation helps identify waste without discarding useful 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.
- Software inventory and its costs: Explain what counts as software inventory and why it is costly before it delivers a completed outcome.
Why it matters: Unfinished work can consume effort even when it has not yet delivered value. - Permanent temporary code paths: Describe how a temporary feature-flag split becomes inventory and why the unfinished decision makes changes harder.
Why it matters: A temporary choice left unresolved can turn every later change into work on multiple paths.
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.
- Motion waste and attention: Explain what motion waste looks like in software, how it differs from transport, and why small interruptions add up.
Why it matters: Recognizing these small attention costs makes an otherwise hard-to-see form of waste visible. - Missing context in artifacts: Explain how artifacts that omit intent create motion waste, using the logging example, and why the section treats this as a system-design problem.
Why it matters: Improving the context carried by artifacts reduces repeated investigation rather than asking individuals to search faster.
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.
- Hidden and compounding waiting: Explain why waiting in software development may not look like idleness and how delayed feedback affects lead time and rework.
Why it matters: A busy team can still be losing time to waits it has learned to work around. - Validation feedback timing: Describe how validation tied to slow, high-cost dependencies creates waiting, and distinguish timely feedback from test coverage.
Why it matters: Earlier validation lets developers respond while the change is still fresh in their minds.
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.
- Software overproduction and hidden costs: Explain what overproduction looks like in software and why it is wasteful even though it can look like progress.
Why it matters: More code can increase the work of maintaining a system without delivering more value. - Timing of future-proof abstractions: Explain why a technically sound abstraction can still be overproduction, and describe how to question whether it is justified now.
Why it matters: Questioning future-proofing can prevent a plausible design from becoming lasting overhead.
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.
- Overprocessing versus overproduction: Explain why work can be wasteful even when it is used, and distinguish overprocessing from overproduction.
Why it matters: It helps you recognize waste in a working solution, not just in work that goes unused. - Unjustified structure and its costs: Describe how to question added structure in a solution and explain the costs it can impose even when the design looks professional.
Why it matters: A design that looks extensible can quietly make each future change harder.
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.
- Visible and subtle defects: Explain that defects require rework or keep a product from meeting expectations, and that they can include plausible-looking code that fails in some contexts. Describe how AI-generated code can conceal incorrect assumptions despite passing happy-path tests.
Why it matters: Recognizing plausible-looking failures helps you see defects before they become expensive rework. - Workarounds as defect waste: Explain why short-term workarounds for known defects can become lasting waste when their underlying causes go unexamined. Describe the resulting friction, cognitive load, and loss of trust.
Why it matters: A workaround may keep the system running while quietly making every future change harder.
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.
- Unused talent in software: Explain what unused talent looks like in a software team and why even important work can waste an engineer’s expertise.
Why it matters: It helps you spot waste that can be hidden behind necessary-looking work. - Systemic cost of compensation: Describe how compensating for other wastes can become an expectation and why relying on experienced people to do so makes a system fragile.
Why it matters: A system that works only because experts repeatedly rescue it may be hiding a structural problem.
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.
- Systemic waste and hidden friction: Explain why waste can persist even when capable people are trying to do good work, and how adaptations can conceal its causes.
Why it matters: Seeing friction as a system problem makes it possible to improve its causes rather than blame the people compensating for it. - Observation grounded incremental improvement: Describe how Gemba and Kaizen connect observing work where value is created with making small, continuous improvements.
Why it matters: Observing real work helps improvements address how the system actually operates.
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.
- Gemba as observed work: Explain what the Gemba is in software development and why teams should observe work as it happens before deciding what to change.
Why it matters: Seeing the work firsthand helps a team address real friction rather than a problem inferred from a dashboard. - Kaizen as system improvement: Describe how Kaizen uses small, continuous changes informed by the Gemba, and explain how a team checks whether those changes help.
Why it matters: Small changes grounded in observed work let teams learn and improve without relying on blame or sweeping plans. - Observed CI friction and fixes: Trace how observing a developer using a slow, unstable CI pipeline leads to different improvements from those suggested by build-time metrics alone.
Why it matters: The CI example shows how watching the workflow can reveal better targets for improvement than an apparent need for more compute.
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.
- Pull request work audit: Describe how to audit a recent pull request by listing its work without judgment, then classifying each item as VA, NNVA, or waste.
Why it matters: Listing before judging makes it easier to notice work that might otherwise blend into the PR. - System-focused waste reflection: Explain how to investigate work labeled as waste and reflect on the largest sources of friction without turning the audit into self-blame or an immediate fix.
Why it matters: Looking for system constraints helps turn a frustrating PR into a useful observation rather than a reason for blame.
Key terms: pull request, VA, NNVA, Waste, system constraint, friction
2.7 Summary
Where this is used later
- Understanding flow, from idea to production (chapter 6) · The distinction between work time and elapsed delivery time supports examining flow from idea to production.
- Value-add versus wasteful testing (chapter 5) · Evaluating testing work calls for distinguishing protection of value from waste.
- Where AI creates waste (chapter 3) · The warning about AI-accelerated accumulation motivates examining where AI creates waste.
- Evolving to shift the source of truth (chapter 4) · The distinction among user, business, and technical value.
- AI as a dependency (chapter 4) · The distinction between user, business, and technical value.
- The value of dependencies (chapter 4) · The idea of evaluating work by its business value.
- Spec first: Define before you build (chapter 4) · Connects streaming and stability to technical value.
- (chapter intro) (chapter 3) · Value depends on context rather than an output's appearance alone.
Concepts explained in this chapter
- valueThe benefit users receive from software that meets their needs through usable, reliable behavior.
- wasteWork that creates no customer value and can be eliminated without harming delivery or its outcomes.
- lean principleA management and process-improvement philosophy focused on maximizing customer value, reducing waste, improving flow, and learning continuously.
- continuous improvementA feedback loop is a process in which information about outcomes is returned to influence subsequent decisions or actions.
- GembaThe actual place where work occurs and value is created, viewed in Lean management as the location for direct observation.
- business valueBusiness value is the organizational benefit produced when software reliably supports business outcomes such as reduced support demand and lower operating cost.
- technical valueBenefit that software work provides to the maintainability, safety, operability, or evolvability of a technical system.
- overproduction wasteLean waste caused by producing more, earlier, or sooner than demand requires.
- bugA fault in software that can cause incorrect, unreliable, or unintended behavior.
- waiting wasteLean waste caused by people or work items being unable to proceed while awaiting input, feedback, a decision, or another process step.
- motion wasteLean waste caused by unnecessary physical or cognitive movement while performing work.
- over-processingLean waste caused by doing more work or adding more complexity than is required to deliver the desired outcome.
- unused skillLean waste caused by failing to use people's knowledge, abilities, or judgment to improve outcomes.
- lean lensA perspective for analyzing software delivery in terms of value, flow, pull, quality, and learning.
- eight wastesThe eight Lean categories of waste—transport, inventory, motion, waiting, overproduction, overprocessing, defects, and unused skills—remembered by the mnemonic TIMWOODS.
- flowA Lean principle of moving work continuously by reducing queues, delays, and interruptions.
- riskThe possibility of harm or loss, assessed here through the probability and impact of a failure and the time it remains undetected.
- work in progressWork in progress is the quantity of work that has been started but not yet completed in a process.
- AI-generated codeSource code produced by an artificial-intelligence system from supplied inputs or instructions.
- inventoryInventory is the waste of work items, information, or decisions that have been started or accumulated but are not yet needed downstream.
- capacityThe amount of work a delivery system or team can handle within a given period.
- indirectionAn additional layer of reference or mediation through which software accesses an object, operation, or dependency.
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.
