What you will learn in Build High Value Software Systems
How to eliminate waste across the software delivery lifecycle
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
What you learn in chapter 15 →Concepts explained in this book
- continuous improvementA feedback loop is a process in which information about outcomes is returned to influence subsequent decisions or actions.
- standard workA single prescribed method applied across teams regardless of differences in their work contexts.
- wasteWork that creates no customer value and can be eliminated without harming delivery or its outcomes.
- valueThe benefit users receive from software that meets their needs through usable, reliable behavior.
- flowA Lean principle of moving work continuously by reducing queues, delays, and interruptions.
- overproduction wasteLean waste caused by producing more, earlier, or sooner than demand requires.
- activity ratioThe proportion of elapsed work time spent on productive activity rather than waiting or other non-progressing periods.
- AI-generated codeSource code produced by an artificial-intelligence system from supplied inputs or instructions.
- lean principleA management and process-improvement philosophy focused on maximizing customer value, reducing waste, improving flow, and learning continuously.
- constraintA condition or limitation that restricts how work can proceed within a delivery system.
- specificationA specification is a documented statement of required software behavior, constraints, or qualities.
- intentThe desired outcome, requirements, and rationale that guide software implementation.
- value streamA value stream is the complete sequence of activities and handoffs through which work produces an outcome for a customer or user.
- cause analysisA systematic process for identifying the underlying causes of a problem or failure rather than addressing only its symptoms.
- work in progressWork in progress is the quantity of work that has been started but not yet completed in a process.
- GembaThe actual place where work occurs and value is created, viewed in Lean management as the location for direct observation.
- dependencyA software component or package that another component requires to build or operate.
- pull modelA Lean principle in which work is started in response to readiness or actual demand rather than being pushed into the system prematurely.
- CPU timeThe time spent actively progressing a change through activities such as coding, testing, fixing, and reviewing.
- contractAn application programming interface is a defined set of operations and rules through which software components interact.
- learning principleA Lean principle of using feedback, operational experience, and failures to improve the delivery system.
- inventoryInventory is the waste of work items, information, or decisions that have been started or accumulated but are not yet needed downstream.
- wip limitA rule that caps the number of work items that may be in progress at once.
- code reviewThe practice of examining proposed source-code changes for correctness, design, and maintainability.
- over-processingLean waste caused by doing more work or adding more complexity than is required to deliver the desired outcome.
- bottleneckA stage whose capacity persistently falls short of demand and limits the output of a value stream.
- cycle timeThe elapsed time required for work to move through a production or delivery process.
- lead timeThe elapsed time between the start of work and delivery of its result.
- ai coding assistantA software tool that uses artificial intelligence to help generate, transform, explain, or review code.
- AndonA visual management system that signals abnormal conditions so work can be stopped or corrected.
- lean lensA perspective for analyzing software delivery in terms of value, flow, pull, quality, and learning.
- AI assistanceAI-assisted development is software development in which artificial-intelligence systems support activities such as coding, design, testing, or documentation.
- jidokaA Lean production approach that builds quality into processes by stopping when abnormalities occur and preventing defects from proceeding.
- test-driven developmentA development practice in which failing tests are written before implementation and then used to guide code until the tests pass.
- standardA standard is an agreed rule or specification that expresses intended behavior or practice.
- software testingA procedure that evaluates software behavior against expected results under specified conditions.
- A3 reportA structured Lean problem-solving approach that documents an issue, its analysis, and proposed countermeasures in a concise report.
- artificial intelligenceArtificial intelligence is the field of computational methods that perform tasks associated with human perception, reasoning, learning, or goal-directed action.
- kaizen cardA record of a proposed process improvement that specifies its baseline, change, owner, and target outcome.
- change failure rateThe proportion of software changes that cause a failure requiring remediation, rollback, or another corrective response.
- mean time to resolutionThe average time required to restore a system or service after an incident.
- value stream mappingA Lean technique for representing and analyzing the flow of work through a value stream.
- integration testA test that verifies interactions among software components or between software and an external system.
- qualityThe degree to which software satisfies its requirements and is free from defects.
- control chartA statistical process-control chart that plots process data over time against a center line and control limits to distinguish common-cause variation from unusual variation.
- bugA fault in software that can cause incorrect, unreliable, or unintended behavior.
- friction logA record of workflow friction, such as waits, context switches, manual steps, and moments of confusion.
- YAGNI principleA software design discipline that delays adding structure until a concrete requirement demonstrates the need for it.
- psychological safetyPsychological safety is a shared belief that people can raise concerns, ask questions, and propose changes without being punished or humiliated.
- collective ownershipA team practice in which responsibility for maintaining and changing software is shared across team members rather than assigned to isolated specialists.
- 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.
- automationThe use of software or machines to perform tasks with reduced manual intervention.
- theory of constraintsA management discipline that improves system performance by identifying and addressing the constraint that limits throughput.
- is/is not analysisA problem-analysis technique that compares where, when, and under what conditions a problem occurs with conditions where it does not.
- Five WhysA root-cause analysis technique that repeatedly asks why a problem occurred, using each answer to guide the next question.
- pair programmingA collaborative software-development practice in which two people work together on the same task, typically sharing one computer.
- retrospectiveA team meeting for reflecting on recent work and identifying improvements.
- takt timeThe available time per unit of output, calculated by dividing the available production window by demand in that window.
- scaffoldA temporary partial implementation that establishes structure while leaving some behavior incomplete or explicitly marked for later work.
- countermeasureA countermeasure is an action designed to address a problem’s cause and prevent or reduce its recurrence.
- acceptance criteriaVerifiable conditions that an output or implementation must satisfy to be considered acceptable.
- load testingTesting that evaluates system behavior and performance under a specified workload.
- synchronous callProcessing in which an operation waits for current work to complete before proceeding or returning.
- fishbone diagramA cause-analysis diagram that places a problem at the head of a central spine and branches potential causes into categories.
- fix-prevent-detect testA completeness pattern for addressing a problem by fixing its immediate effects, preventing recurrence, and detecting conditions that still arise.
- batch sizeThe number of work items grouped together for processing or delivery as one batch.
- throughputThe rate at which completed work passes through a production or delivery system.
- queue timeThe elapsed time a work item spends waiting rather than being actively processed.
- poka-yokePoka-yoke is a mistake-proofing technique that uses a physical or logical barrier to prevent an error from occurring.
- business ruleA business rule is a domain-specific requirement that governs decisions, constraints, or behavior in a software system.
- blameless postmortemA blameless retrospective is a structured review of an incident that focuses on system conditions and improvements rather than individual fault.
- entry criterionAn entry criterion is a condition that work must satisfy before implementation begins.
- unit testAn automated test that verifies the behavior of a small isolated unit of software.
- last responsible momentA decision-making principle of postponing a decision until the latest point at which it can still be made responsibly, allowing more information to become available.
- unused skillLean waste caused by failing to use people's knowledge, abilities, or judgment to improve outcomes.
- refactoringRefactoring is the restructuring of existing software without changing its externally observable behavior.
- precommit hookA pre-commit hook is an automated check that runs before a version-control commit is created.
- visual managementA system that makes the current state of work visible to the people responsible for it.
- Andon cordA cord that a worker pulls to signal an abnormality and prompt immediate attention or correction.
- couplingA dependency relationship in which one software component relies on another component's structure, behavior, or availability.
- delivery loopA software-delivery model that cycles from intent through coding, building and testing, running, and observing back to intent.
- backpressureA mechanism by which a downstream system signals that upstream work should be slowed or limited to match its processing capacity.
- metricA metric is a quantitative measure of a property or outcome of a process, system, or activity.
- flaky testA test whose result is nondeterministic despite unchanged software and test inputs.
- cognitive attack surfaceThe set of ways that AI-generated or AI-mediated information can introduce uncertainty, inconsistency, or harmful influence into human reasoning and software decisions.
- legacy codeLegacy code is existing software that a team inherits and must understand or change, regardless of whether it is still useful and operational.
- waiting wasteLean waste caused by people or work items being unable to proceed while awaiting input, feedback, a decision, or another process step.
- characterization testingA characterization test records and verifies the observed behavior of existing software, including behavior that may be undocumented.
- abstractionA software-design technique that hides implementation details behind a simplified model or interface.
- vanity metricA measure that can appear to indicate success without showing whether the system’s outcomes actually improve.
- software deliverySoftware delivery is the process of moving software from intent through implementation and validation to usable outcomes.
- reworkRework is the additional engineering effort required to revise or redo work because it does not satisfy newly discovered or changed requirements.
- motion wasteLean waste caused by unnecessary physical or cognitive movement while performing work.
- executable documentationDocumentation expressed in executable or automatically checked artifacts so it can be verified against the system.
- set-based designAn engineering approach that explores multiple design options in parallel, narrows them as evidence arrives, and delays commitment until further exploration is no longer worthwhile.
- behavior-driven developmentA development practice that specifies and tests software behavior in a form intended to be readable by both technical and non-technical stakeholders.
- interface-oriented designA software-design approach that organizes components around explicit interfaces separated from their implementations.
- pull-based designA design pattern in which concrete requirements pull only the structure needed to satisfy them into a codebase.
- AI-resilient workflowA workflow designed to continue meeting its requirements despite changes or inconsistency in AI tool behavior.
- baselineAn initial measurement of a process or system that provides a reference for comparison with later measurements.
- templateA prompt template is a reusable instruction structure containing fixed guidance and variable inputs for an AI system.
- muraUnevenness or variability in workload or process conditions that disrupts smooth production flow.
- postincident analysisA post-incident review is a structured examination of an operational incident and the conditions that allowed it to occur.
- change frequencyChange frequency is how often a software component is modified over a given period or set of releases.
- cognitive debtAccumulated difficulty caused by code and design decisions that developers do not fully understand or own.
- pattern fragmentationThe divergence of implementation patterns across features that should follow a consistent architectural or coding approach.
- nondeterminismThe property of behavior that can produce different outcomes for the same input because of probabilistic processes or varying execution conditions.
- metric gamingThe behavior of optimizing a measured number to meet its target without improving the underlying outcome.
- paired metricA measure considered alongside another measure that guards against harmful changes to the underlying system.
- checklistA list of items or steps that can be checked to support consistent completion of a task or process.
- experimentationA deliberately limited activity undertaken to learn about an uncertain idea or approach.
- surface areaThe set of interfaces, behaviors, integration points, and change obligations exposed by a software component or dependency.
- onboardingOnboarding is the process of helping a new team member become able to perform and deliver work within an organization.
- headroomUnused system capacity reserved to absorb changes or variation in demand without degrading service.
- dead letter queueA queue that holds messages or work items that could not be processed successfully through the normal path.
- SLEAn internal expectation that states the level of service performance a team expects its system to deliver.
- code coverageA measure of which code elements, such as lines, branches, or functions, are executed during testing.
- riskThe possibility of harm or loss, assessed here through the probability and impact of a failure and the time it remains undetected.
- test suiteA collection of tests executed to evaluate software behavior or quality.
- architecture decision recordAn architecture decision record is a concise document that records an architectural decision, its rationale, and its consequences.
- measure-change-measure cycleA recurring process of observing work, measuring it, making a change, and measuring again.
- pareto analysisA prioritization technique that ranks causes by frequency or impact so that attention can focus on the few causes responsible for most problems.
- muriMuri is overburden that occurs when demand exceeds a system’s capacity, leaving insufficient margin to absorb variation.
- test layerA level in a testing strategy that checks software for a particular class of failures at a characteristic speed and scope.
- technical debtTechnical debt is the future cost created by implementation choices that make a system harder, riskier, or more expensive to change or operate.
- runbookA runbook is a documented set of operational procedures for diagnosing, mitigating, or recovering from known system conditions.
- quality principleA Lean principle of building correctness and defect prevention into work rather than relying on later inspection.
- value and pull principleThe value and pull principle is a Lean principle that starts work only when its value and readiness are sufficiently established.
- source of truthThe artifact or signal that a team treats as authoritative for determining correctness, completion, and resolving disagreements.
- seamA place in a software system where behavior can be altered or substituted without changing the code at that point.
- system boundaryA boundary is a separation between system parts, representations, ownership areas, or organizational responsibilities across which information or work passes.
- commitmentA lasting investment in software work or artifacts that makes change, replacement, or deletion costly.
- kaizen burstA visual marker on a value stream map that identifies a focused improvement intervention.
- merge blockerA review criterion or condition that prevents a proposed code change from being merged until the issue is resolved.
- perfectionIn Lean, an unattainable ideal represented by continuously reducing defects and waste through systematic improvement.
- friction per changeThe additional time or effort a code smell causes for each modification to the affected code.
- queue depthThe number of work items waiting in a queue for downstream processing.
- strangler fig patternA gradual replacement pattern in which a new system is built alongside a legacy system and takes over its responsibilities incrementally.
- indirectionAn additional layer of reference or mediation through which software accesses an object, operation, or dependency.
- delivery systemA delivery system is the interconnected set of people, tools, automation, and processes through which work moves from creation to operational outcome.
- eight wastesThe eight Lean categories of waste—transport, inventory, motion, waiting, overproduction, overprocessing, defects, and unused skills—remembered by the mnemonic TIMWOODS.
- feedbackInformation about the effects or results of work that can guide subsequent decisions or changes.
- respect for peopleA system property in which people closest to the work have the authority, information, and psychological safety to improve it.
- flow protectionAn upstream quality-control technique that prevents defects, variability, and waste from entering a software delivery flow.
- single-piece flowA production approach in which one item moves through the system at a time so defects can be detected and corrected before the next item is produced.
- executable runbookAn operational procedure whose diagnostic steps are implemented as code that can run automatically and present results for human decisions.
- capacityThe amount of work a delivery system or team can handle within a given period.
- bounded contextA clearly defined boundary within which a domain model and its terminology have a consistent meaning.
- domain eventA record of a significant occurrence in a business domain that other parts of a system can respond to.
- personaA structured brief that shapes an AI assistant's responses toward specified characteristics, principles, or standards.
- pipelineA sequence of stages through which a software change moves during delivery or deployment.
- SOLID principlesA set of five software design principles intended to make code easier to change.
- kaizen eventA focused, time-boxed effort in which a team works intensively to improve a specific process problem.
- quality gateA quality gate is a defined verification point that determines whether work satisfies specified quality conditions before proceeding.
- server streamingServer-side streaming is the incremental transmission of generated data from a server to a client rather than buffering the complete result.
- process variationFluctuation in a process’s measured outcomes over time or across operating conditions.
- autonomyControl over how one works and the ability to exercise judgment in defining and solving problems.
- intrinsic motivationMotivation that arises from internal drivers rather than external rewards or pressure.
- masteryThe development of skill and capability through progressively challenging work.
- purposeA connection between one's work and a meaningful goal beyond the immediate task.
- component rotationA practice of assigning developers to work on components outside their usual areas of responsibility for a limited period.
- cross reviewA review practice in which someone other than the change's primary author examines the proposed change.
- code generationThe production of source code from a specification, model, template, or other structured input.
- inventory wasteLean waste consisting of work, materials, or information held before they are needed by the next process.
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.
