- Series: Enterprise Software Development
- Paperback: 120 pages
- Publisher: lulu.com (March 1, 2010)
- Language: English
- ISBN-10: 0557138329
- ISBN-13: 978-0557138326
- Product Dimensions: 6 x 0.3 x 9 inches
- Shipping Weight: 8.3 ounces (View shipping rates and policies)
- Average Customer Review: 20 customer reviews
- Amazon Best Sellers Rank: #126,970 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
+ Free Shipping
+ Free Shipping
+ $3.99 shipping
Kanban and Scrum - making the most of both (Enterprise Software Development) Paperback – March 1, 2010
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Customers who bought this item also bought
Customers who viewed this item also viewed
Henrik Kniberg is one of those rare people who can extract the essence of a complicated situation, sort out the core ideas from the incidental distractions, and provide a crystal clear explanation that is incredibly easy to understand.
Exceptional. Really enjoyed it. Very objective.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
"Kanban and Scrum" is about 100 pages and consists of 2 parts, each written by one of the two authors. The first part is the "Kanban and Scrum" part, written by Henrik, where he shortly clarifies Scrum and Kanban and explains the differences between them. He gives hints to in which situation Kanban and which situation Scrum might be better... and also hints about ways of combining them into Scrumban (a term Henrik doesn't use, but was popularized by one of the first descriptions of Kanban by Corey Ladas Scrumban - Essays on Kanban Systems for Lean Software Development).
The second part of this book is an experience report written by Mattias Skarin about applying Kanban for an operations team in a games company. He briefly explains how they got started and how gradually they evolved Kanban and the kind of decisions they had to make.
This book is very thin and reads fast (of the 100 pages, there are a lot of empty pages). Most of it is available for free from Henrik's page, so if you don't want to buy the book, you can just download it :) The writing is easy to read, it reads more like a blog post than a book.
Amazon stars-wise, I've been thinking about 3 or 4 stars. 3 stars because the book is thin, not very thorough and it does what it is supposed to do well, but not much more. It doesn't give a thorough introduction of Kanban (for that, probably check David Andersons work: Kanban) it doesn't give a thorough introduction of Scrum either. It just briefly explains the difference. Four stars because Henriks writing is very popular (a little too popular for me) but it attracts a wide audience. Also, his writing is very clear, he has a good ability to explain seemingly complex concepts in a simple way. Yet, this book is not a ground-shaking new book. In the end, I decided to favor Henriks explanation skills and go for 4 stars. If you know about Scrum and heard about Kanban and... wonder... then this is the book for you! If you want to have a thorough explanation of Kanban or Scrum, skip this book and go for the ones mentioned in this review.
As the authors put it in the opening.. "it's not the tool you start with, but the way you constantly improve your use of that tool and expand your toolset over time". In other words, Scrum, or any other methodology should not be treated as a dogma. Great teams review, adjust, and experiment with their process to discover what works for them and their environment. Scrum provides a set of guidelines, and Kanban relaxes some of them, giving you more wiggle room (which can be both a blessing and a curse) to explore: how you estimate, how you prioritize, which criteria you optimize (lead time vs troughput vs ...), whether you hold daily standups, and so on.
The book is a quick read and provides a good mix of hands-on examples and practical advice. The reassuring part was that our team has already arrived at many of the same conclusions and patterns on our own, and this just gave us the confidence to go even further and experiment with our workflow to a larger extent.
When I sit on the couch and open it casually, I can't stop.
This book gives you a clear understanding of the differences between Scrum and Kanban, and the combination of both.