liveBook · Manning

Chapter 6: Flow in your development cycle

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

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.

After this chapter you will be able to

What it builds on

Section by section

Introduction

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.

Key terms: development value stream, idea, working behavior in production, inventory, work in progress, unshipped work, flow, velocity, story points

6.1 Understanding flow, from idea to production

Defines development flow as the movement of an idea through the full value stream to working behavior in production, showing why fast coding can coexist with slow delivery.

Key terms: value stream, flow, working behavior in production, value-adding work, necessary but non-value-adding work, pure waste, process time, wait time, activity ratio, queue depth

6.1.1 Multiple value streams

This section distinguishes several software-delivery value streams and shows why improving flow requires mapping the real process rather than relying on the documented one.

Key terms: feature value stream, defect value stream, deployment value stream, value stream map, waits, rework loops, queues, time metrics

6.1.2 The metrics value stream

Shows how timing data on software value stream maps exposes waiting and helps teams target the constraint that most delays delivery.

Key terms: value stream map (VSM), metrics value stream, timestamps, queue aging, feature value stream, lead time, cycle time, activity ratio, defect value stream, deployment value stream

6.1.3 The tip of the iceberg

The section expands the value stream beyond engineering delivery and shows why delays anywhere between an idea and user benefit govern flow.

Key terms: value stream, value delivery, flow, system metric, hidden dependencies, Kaizen bursts

6.2 Reducing batch sizes for faster feedback

This section explains how smaller, single-concern pull requests speed feedback and flow, while warning that many small changes can still create inventory.

Key terms: batch size, pull request, cycle time, lead time, value stream, refactor, unit of value, flow, small batches, inventory

6.3 Limiting work in progress

This section explains how limiting unfinished software work protects delivery, changes the response to blockers, and makes constraints visible.

Key terms: work in progress (WIP), inventory waste, WIP limit, blockers, swarm, Kanban, pull system, downstream capacity, standard work, gemba

6.4 Identifying and avoiding bottlenecks

This section explains how a capacity-constrained stage governs delivery flow, creates queues and waste, and should be the focus of improvement.

Key terms: Theory of Constraints (ToC), constraint, throughput, bottleneck, value stream, review capacity, queue depth, lead time, aging work items, waiting

6.4.1 Elevating the constraint

This section explains why improving throughput requires elevating the binding constraint while aligning upstream work with its capacity.

Key terms: ToC, constraint, throughput, elevating a constraint, binding constraint, subordination, shared staging environment, environment throughput, lead time

6.4.2 Designing the future value stream

The section shows how to design a measurable future value stream that removes waiting caused by a scheduling constraint.

Key terms: Current State Value Stream, Future State Value Stream, standard work, lead time, cycle time, meeting cadence, waiting waste, temporal, countermeasure, rotating breakdown coverage

6.5 CI/CD: Flow enabler or disruptor?

This section distinguishes faster CI/CD from end-to-end flow and shows that automation can either help or disrupt the movement of changes toward delivery.

Key terms: CI/CD, flow, feedback loops, queue depth, validation delay

6.5.1 CI/CD as flow enabler

This section explains how fast, reliable CI/CD improves flow by removing waiting and release gates rather than making engineers code faster.

Key terms: CI/CD, optimal validation, feedback loops, small batches, deploy-on-merge, release window, waiting waste, inventory, lead time, blast radius

6.5.2 CI/CD as flow disruptor

This section shows how an overloaded CI/CD pipeline can become the bottleneck in development flow, even when its validation work is valuable.

Key terms: validation runtime, constraint, value stream, feedback, inventory, deep validation, sequencing, alignment, overprocessing, waiting

6.5.3 A balanced scorecard for flow-centric CI/CD

This section explains how to judge whether a CI/CD pipeline protects flow by balancing speed, quality, and stability rather than optimizing one metric.

Key terms: balanced scorecard, flow, validation, coverage, merge-to-production lead time, defect escape rate, pipeline runtime, overprocessing

6.5.4 Lean release strategies: Designing flow beyond deployment

The section explains how separating deployment from release keeps work flowing to users, and why teams must move toward that model incrementally.

Key terms: deployment, release, controlled exposure, feature flags, batch size, Lean release, Kaizen, observability, constraint, future state

6.6 Exercise: Trace one feature and remove one delay

This exercise guides readers to map a shipped feature’s path, find its longest structural delay, and test a small change to improve flow.

Key terms: lead time contribution, cycle time, queue depth, batch size, lead time, activity ratio, constraint candidate, structural delay, Kaizen burst, elevated the constraint

6.7 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 5: Testing as waste prevention Chapter 7: Taming legacy code →

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.