Scrum 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.
Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams.
Consistent with the style of “Scrum and XP from the Trenches”, this book strikes a conversational tone and is bursting with practical examples and pictures.
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
120 pages, 6" x 9", ISBN: 978-0-557-13832-6
Author(s): Henrik Kniberg, Mattias Skarin
Publisher: InfoQ
Year: 2010
Language: English
Pages: 122
FOREWORD BY MARY POPPENDIECK .......................................... v
FOREWORD BY DAVID ANDERSON .............................................. vii
INTRODUCTION ................................................................................... xi
PART I – COMPARISON ....................................................................... 1
1. What is Scrum and Kanban anyway? .................................................. 3
2. How do Scrum and Kanban relate to each other?................................ 7
3. Scrum prescribes roles ....................................................................... 11
4. Scrum prescribes timeboxed iterations .............................................. 13
5. Kanban limits WIP per workflow state, Scrum limits WIP per
iteration .............................................................................................. 15
6. Both are empirical ............................................................................. 17
7. Scrum resists change within an iteration ........................................... 23
8. Scrum board is reset between each iteration ..................................... 25
9. Scrum prescribes cross-functional teams .......................................... 27
10. Scrum backlog items must fit in a sprint ........................................... 29
11. Scrum prescribes estimation and velocity ......................................... 31
12. Both allow working on multiple products simultaneously ................ 33
13. Both are Lean and Agile .................................................................... 35
14. Minor differences .............................................................................. 37
15. Scrum board vs Kanban board – a less trivial example ..................... 41
16. Summary of Scrum vs Kanban .......................................................... 49
PART II – CASE STUDY ...................................................................... 53
17. The nature of technical operations .................................................... 55
18. Why on earth change? ....................................................................... 57
19. Where do we start? ............................................................................ 59
20. Getting going ..................................................................................... 61
21. Starting up the teams ......................................................................... 63
22. Addressing stakeholders .................................................................... 65
23. Constructing the first board ............................................................... 67
24. Setting the first Work In Progress (WIP) limit .................................. 71
KANBAN AND SCRUM - MAKING THE MOST OF BOTH
iv
25. Honoring the Work In Progress (WIP) limit ..................................... 73
26. Which tasks get on the board? .......................................................... 75
27. How to estimate? ............................................................................... 77
28. So how did we work, really? ............................................................. 79
29. Finding a planning concept that worked ........................................... 83
30. What to measure? .............................................................................. 87
31. How things started to change ............................................................ 91
32. General lessons learned ..................................................................... 97
FINAL TAKE-AWAY POINTS ......................................................... 101
ABOUT THE AUTHORS ................................................................... 103
