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.
The Italian translation of this book has been realized by Fabio Armani
- 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.
Example of a Kanban Board where are shown the WIP limits
Here's an excerpt from the book by Henrik Kniberg and Mattias Skarin showing a typical scenario:
- Jim: "Now we've finally gone all-out Scrum!"
- Fred: "So how's it going?"
- Jim: "Well, it's a lot better than what we had before..."
- Fred: "...but?"
- Jim: "... but you see we are a support & maintenance team."v
- Fred: "yes, and?"v
- Jim: "Well, we love the whole thing about sorting priorities in a product backlog, self-organizing teams, daily scrums, retrospectives, etc...."
- Fred: "So what's the problem?"
- Jim: "We keep failing our sprints"
- Fred: "Why?"
- Jim: "Because we find it hard to commit to a 2 week plan. Iterations don't make to much sense to us, we just work on whatever is most urgent for today. Should we do 1 week iterations perhaps?"
- Fred: "Could you commit to 1 week of work? Will you be allowed to focus and work in peace for 1 week?"
- Jim: "Not really, we get issues popping up on a daily basis. Maybe if we did 1 day sprints..."
- Fred: "Do your issues take less than a day to fix?"
- Jim: "No, they sometimes take several days"
- Fred: "So 1-day sprints wouldn't work either. Have you considered ditching sprints entirely?"
- Jim: "Well, frankly, we would like that. But isn't that against Scrum?"
- Fred: "Scrum is just a tool. You choose when and how to use it. Don't be a slave to it!"
- Jim: "So what should we do then?"
- Fred: "Have you heard of Kanban?"
- Jim: "What's that? What's the difference between that and Scrum?"
- Fred: "Here, read this book!"
- Jim: "But I really like the rest of Scrum though, do I have to switch now?"
- Fred: "No, you can combine the techniques!"
- Jim: "What? How?"
- Fred: "Just read on..."
About the Authors
Henrik Kniberg & Mattias Skarin are consultants at Crisp in Stockholm (www.crisp.se).
They share a passion for helping companies succeed with Lean and Agile software development in practice,
and balance their time between coaching, teaching, and writing. Henrik's previous book "Scrum and XP from the Trenches"
has over 150,000 readers and is used as the primary guide to Agile software development by hundreds of companies worldwide.
Courtesy of Henrik Kniberg, Mattias Skarin and InfoQ.com,
we're happy to offer a free version for download of the book "InfoQ: Kanban and Scrum - making the most of both",
to get this knowledge in as many peoples hands as possible.
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:
120 pages, 6" x 9", ISBN: 978-0-557-13832-6
- 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
- Forwards by Mary Poppendieck and David J. Anderson
The Italian translation of this book was done by Fabio Armani -
the book's download is available in different formats: .pdf, (.mobi) Kindle, (.pub) iPad, iPhone, iPod touch ...
Note: in the format .mobi/kindle, using reader softwares with which it was tested, there are leaks of information and
formatting due to format conversion.
It is recommended to readers, therefore, preferably use the format .pdf
Download PDF version
Download Kindle version (.mobi)
Download iPad/iPhone version (.ePub)