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  64
23. Constructing the first board . 67
24. Setting the first Work In Progress (WIP) limit  71
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