Kanban and Scrum - Making the Most of BothScrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other? The purpose of this book is to clear up the fog, so you can figure out how Kanban and Scrum might be useful in your environment. Part I illustrates the similarities and differences between Kanban and Scrum, comparing for understanding, not for judgement. There is no such thing as a good or bad tool - just good or bad decisions about when and how to use which tool. This book includes: - Kanban and Scrum in a nutshell - Comparison of Kanban and Scrum and other Agile methods - Practical examples and pitfalls - Cartoons and diagrams illustrating day-to-day work - Detailed case study of a Kanban implementation within a Scrum organization Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams. |
Contents
COMPARISON | 1 |
What is Scrum and Kanban anyway? | 3 |
How do Scrum and Kanban relate to each other? | 7 |
Scrum prescribes roles | 11 |
Scrum prescribes timeboxed iterations | 13 |
Kanban limits WIP per workflow state Scrum limits WIP per iteration | 15 |
Both are empirical | 17 |
Scrum resists change within an iteration | 23 |
Minor differences | 37 |
Scrum board vs Kanban board a less trivial example | 41 |
Summary of Scrum vs Kanban | 49 |
CASE STUDY | 53 |
The nature of technical operations | 55 |
Why on earth change? | 57 |
Where do we start? | 59 |
Getting going | 61 |
Scrum board is reset between each iteration | 25 |
Scrum prescribes crossfunctional teams | 27 |
Scrum backlog items must fit in a sprint | 29 |
Scrum prescribes estimation and velocity | 31 |
Both allow working on multiple products simultaneously | 33 |
Both are Lean and Agile | 35 |
Starting up the teams | 63 |
Addressing stakeholders | 65 |
Constructing the first board | 67 |
Setting the first Work In Progress WIP limit | 71 |
Common terms and phrases
Agile Manifesto Agile methods Agile software development average lead Backlog Selected Develop bottleneck burndown charts cadence capacity column commit constraints continuous improvement cross-functional teams cumulative flow diagram cycle Daily Scrum daily standup meeting decide Deploy Live Develop 2 Deploy example experiment eXtreme Programming feedback loop Fred Henrik Kniberg impediments Issue tracking system iteration planning Kanban board Kanban teams Lean and Agile managers Mary Poppendieck Mattias Skarin means metrics Miyamoto Musashi nice number of items Ongoing Done:0 optimize optional organization pair programming predictability problem process improvement product backlog product owner Progress WIP pull queue release plans retrospective roles Scrum and Kanban Scrum board Scrum prescribes Scrum team self-organizing software development specific sprint backlog stakeholders started story points stuff support team system administration team team chooses team members Test things timeboxed iterations Total velocity typically Visualize week WIP limit workflow workshop
