Overview¶

This guide explores how Lean thinking (originating from Toyota's manufacturing system) complements and strengthens Scrum practice — giving practitioners a vocabulary and toolset for eliminating waste and optimizing flow that Scrum alone doesn't fully prescribe.

Who it's for: Scrum practitioners who want to deepen their process-improvement toolkit with Lean principles.

Core Topics Breakdown¶

1. Lean's Core Principles Applied to Software Delivery¶

• Eliminate waste: identify and remove the seven classic wastes (originally from manufacturing, adapted to knowledge work): partially done work, extra features, relearning, handoffs, task switching, delays, and defects.
• Amplify learning: short feedback loops (a Sprint is itself a Lean feedback loop) and build-measure-learn cycles.
• Decide as late as possible: defer irreversible decisions until the last responsible moment, when you have the most information — directly supports Scrum's iterative planning approach.
• Deliver as fast as possible: favor small batch sizes (a single story) over large batch releases, reducing risk and feedback delay.
• Empower the team: decisions should be made by those closest to the work — mirrors Scrum's self-management principle.
• Build integrity in: quality is built into the process (continuous integration, automated testing, Definition of Done) rather than inspected in at the end.
• See the whole: optimize the entire value stream, not just individual team throughput — a common failure mode is a fast development team blocked by a slow, unaddressed downstream approval process.

2. Value Stream Mapping¶

• A technique for visualizing every step (and every wait/handoff) between "idea" and "value delivered to the customer."
• Distinguishing value-add time (actual work) from non-value-add time (waiting, handoffs, approvals) — often the majority of total lead time in real organizations.
• Using value stream mapping findings to prioritize process-improvement backlog items alongside product backlog items.

3. Kanban as a Lean-Derived Complement to Scrum¶

• Work-in-Progress (WIP) limits as a direct application of "limit batch size" — forcing a team to finish work before starting new work.
• Cumulative Flow Diagrams as a Lean-style visualization tool for spotting bottlenecks.
• "Scrumban" — a hybrid combining Scrum's cadence and roles with Kanban's flow-based visualization and WIP limits.

4. Continuous Improvement (Kaizen)¶

• Small, frequent, team-driven improvements rather than large infrequent process overhauls.
• The Scrum Retrospective as a built-in Kaizen ritual — but Lean adds rigor around making improvements measurable and tracked to completion.

5. Applying Lean Metrics Alongside Scrum Metrics¶

• Lead time: total time from request to delivery (includes waiting).
• Cycle time: time actively spent working on an item once started.
• Both metrics complement (rather than replace) Scrum's velocity, offering a customer-centric view of speed that velocity alone doesn't capture.

Study Tips¶

• Practice drawing a value stream map for a real (or hypothetical) request, labeling each step as value-add or non-value-add, and calculating the percentage of total time that's actually value-add (it's often surprisingly low).
• Be able to name and briefly define all seven classic wastes as applied to knowledge work.
• Practice distinguishing lead time from cycle time with a worked numeric example.

Common Pitfalls¶

• Optimizing team-level velocity while ignoring a slow, unaddressed downstream process (e.g., a lengthy manual QA or compliance review) — a classic "see the whole" failure.
• Treating Kaizen/retrospective improvements as optional "nice to have" rather than tracked, prioritized backlog work.
• Confusing lead time and cycle time in reporting, which misrepresents how responsive the team actually is to new requests.

Quick Reference Cheat Sheet¶

Further Practice¶

Map the last 5 items your team delivered from "requested" to "delivered," and calculate the ratio of value-add time to total lead time.