Scrum and Kanban are two of the best known lean/agile software project management frameworks. The mini-book Kanban and Scrum: making the best of both compares and contrasts these two process frameworks and breaks them down into a set of tools that can be mixed and matched to construct a wide range of hybrid processes.
Resource information | Details |
---|---|
Book title | Kanban and Scrum: making the best of both |
Authors | Henrik Kniberg, and Mattias Skarin |
Publication | 2010, ISBN: 978-0-557-13832-6 |
Many books have been written on lean and agile software project management methods1,2,3. Currently, two of the most popular process frameworks for lean/agile software projects are Scrum1 and Kanban. The mini-book Kanban and Scrum: making the best of both does an excellent job of providing a succinct overview of Scrum and Kanban and compares and contrasts how they address different aspects of managing a software development project. They do so in a way that provides deeper insight into these process frameworks than can be gained by just studying them in isolation. The authors break down Scrum and Kanban into a set of tools and process building blocks that can be used to construct custom processes for individual projects. Kanban is likely the least prescriptive framework for lean/agile project/development management that has even been proposed that is based up with solid theory and evidence. By incrementally adding some tools from Scrum, Kanban can be extended and modified to address almost any project and create a continuum of lean/agile project management processes from basic Kanban to full-blow Scrum.
Part I of this mini-book is about 50 pages and provides an excellent overview and discussion of Scrum and Kanban and breaks them down into their pieces to come up with a powerful toolbox of building-blocks. This material is a fast read and provides the basic terminology for discussion of Kanban, Scrum and agile methods in general. Part II of this mini-book is a 50-page case study in the application of these building blocks and experience from a real project. Unlike extended examples in some books, the case study presented in Part II really enhances the material covered in Part I.
This mini-book is packed with helpful diagrams and cartoons that convey the concepts being discussed in a very effective way. Just the diagrams and cartoons alone make this mini-book worth the time to browse and is a great way to refresh these concepts in one's mind.
Considering there are much longer books on lean and agile methods, this mini-book, in my view, provides the best usage of one's time in to get a grip on these concepts with the least amount of investment. I can't recommend this mini-book more strongly if one is interested in improving one's software project management processes using lead/agile methods.
The ideas and insights of this mini-book were used as the foundation for the software development management processes in the CSE Consortium For Advanced Simulation Of Light Water Reactors (CASL)4 project and especially in the Nuclear Reactor Physics Integration Focus area starting in 2010. By using the iterative retrospective process and with experiments, a very successful iteration-based Kanban process was constructed and variations of that process endure in some of the groups that participated in the CASL project after the main 10-year project ended.
At the time of this writing, this mini-book is available for free download from infoq.com but you must register with infoq.com to get it. A printed version of the mini-book that can be mailed to you is also available for a very small fee.
References
-
1Agile Software Development with Scrum
Schwaber, Ken and Mike Beedle. Prentice Hall, 2002 -
2Extreme Programming Explained: Embrace Change (2nd Edition)
Beck, Kent. Addison Wesley, 2004 -
3Implementing Lean Software Development: From Concept to Cash
Poppendieck, Mary and Tom. Addison Wesley, 2006 - 4Consortium For Advanced Simulation Of Light Water Reactors (CASL)