Kanban and Scrum - making the most of both
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
Courtesy of Henrik Kniberg, Mattias Skarin and InfoQ.com, we're happy to offer a free version for download, to get this knowledge in as many peoples hands as possible. Download this book FREE (PDF)
Buy the print version for $22.95
If you enjoyed reading the free download version, please support the author and InfoQ's book series by buying the print version for only $22.95.
Here you can find the translated versions of the book:
- French version, thanks to Claude Aubry, Frédéric Faure, Antoine Vernois & Fabrice Aimetti
- Spanish version, thanks to Ángel Medinilla, Rodrigo Corral, Xavier Quesada-Allue, Jorge Uriarte, Agustín Yagüe, Teo Sánchez, Juan Palacio,Gregorio Mena, Ángel Agueda, Laura Morillo-Velarde, Jorge Jiménez, Javier Sánchez, Juan Quijano
- Japanese version, thanks to Hiroki Kondo and Midori Daida
- Italian version, thanks to Fabio Armani. Kindle and iPhone/iPAd formats available.
- Russian version, thanks to Mariia Yevgrashyna, Tanya Kobzar, Sergiy Movchan, Artjom Serdyuk, Borys Lebeda, Aleksey Solntsev, Alina Marusyk, Alexander Zhovnuvaty, Aleksey Goncharenko, Lina Shishkina, Roman Kononov, Tim Yevgrashyn, Yaroslav Gnatyuk, Andrey Bibichev
- Hungarian version, thanks to Zoltan Csutoras
- Bulgarian version, thanks to Zornitsa Nikolova, Tsvetelina Peteva, Monika Kovachka-Dimitrova, Lyubomir Pashov - Leanify Ltd.
- Portuguese version, thanks to Juliana Berossa Steffen, Marcelo Andrade, Eduardo Bobsin, Rodrigo Russo, Daniel Wildt, Luciano Costa, Renato Willi, Marcos Vinícius Guimarães, Adam Brandizzi, André Pantalião, Cássio Marques, Ismael Stahelin, Rafael Fuchs, Gerson Dias, Ian Gallina, Rafael Dantas, Vitor Machel, Vinicius Assef, Bruno Pedroso, Cassiano Alves, Gustavo Grillo, Igo Coelho, Rafael Prikladnicki, Adriana Luppi.
- German version, thanks to Maria Oelinger
- Persian version, thanks to Masood Ghasemzadeh
- Swedish version, thanks to Johan Natt och Dag
- Chinese version, thanks to Jacky Li
- Slovak version, thanks to Dusan Kocurek
Table of contents
Foreword by Mary Poppendieck
Foreword by David Anderson
PART I – COMPARISON
- So what is Scrum and Kanban anyway?
- So how do Scrum and Kanban relate to each other?
- Scrum prescribes roles
- Scrum prescribes timeboxed iterations
- Kanban limits WIP per workflow state
- Both are empirical
- Scrum resists change within an iteration
- Scrum board is reset between each iteration
- Scrum prescribes cross-functional teams
- Scrum backlog items must fit in a sprint
- Scrum prescribes estimation and velocity
- Both allow working on multiple products simultaneously
- Both are Lean and Agile
- Minor differences
- Scrum board vs Kanban board - a less trivial example
- Summary of Scrum vs Kanban
PART II – CASE STUDY
- The nature of technical operations
- Why on earth change?
- Where do we start?
- Getting going
- Starting up the teams
- Addressing stakeholders
- Constructing the first board
- Setting the first work in progress limit
- Honoring the WIP limit
- Which tasks get on the board?
- How to estimate?
- So how did we work
- Finding a planning concept that worked
- What to measure?
- How things started to change
- General lessons learned
Final Take-aways points
About the Authors