Lean Thinking and Iterative, Incremental Delivery

  • Explain how lean thinking reduces waste and focuses on the essentials
  • Distinguish iterative from incremental delivery and why Scrum uses both
  • Explain why Scrum is a lightweight framework rather than a full methodology

Alongside empiricism, Scrum draws on lean thinking: reduce waste and focus on what is essential. Work that never reaches users, features nobody asked for, long hand-offs and large batches of half-finished work are all forms of waste. Scrum's short Sprints, single ordered Product Backlog and focus on a usable Increment every Sprint are lean ideas in practice.

Scrum combines two ideas in delivery. Incremental means value is delivered in usable pieces, each building on the last. Iterative means the team revisits and improves both the product and the way it works, cycle after cycle. Together they optimize predictability and control risk: every Sprint ends with something real to inspect, so the team, the Product Owner and stakeholders learn from evidence instead of assumptions, and a wrong direction costs a few weeks rather than a year.

Scrum is intentionally incomplete. It defines only the parts needed to put empiricism into practice — the accountabilities, events, artifacts and rules that bind them together — and leaves the team to fill in the practices that fit their work. Changing the core design or skipping parts of it hides problems and limits the benefits; what results may be useful, but it is no longer Scrum.

Study focus: when an answer adds a phase, a role, a document or a "hardening" step that Scrum does not define, it is usually wrong. Scrum is described as a lightweight framework, not a methodology or a process manual.

Key terms in this chapter

Lean thinking · Iterative delivery · Incremental delivery · Scrum framework

Previous: Empiricism and the Three Pillars · Next: The Five Scrum Values

Try the free Scrum Master practice questions · Take the free Scrum Master mock exam