Kanban for skeptics
Kanban for skeptics
Clear answers to Kanban in software development
About the Book
In my daily job as a change agent, I constantly need to reassure people that the path we follow is worthwhile traveling. This need is often expressed in the form of critique and difficult questions. When I coach Agile teams, this is often the case. The same thing happens when introducing Kanban. However, I noticed that Kanban raises much harder questions on a management and leadership level, once people are introduced to the basics and start to explore the subject on their own.
The type of questions Kanban raises, seem to be hard to answer without lapsing into an hour long discussion. I guess this is normal because Kanban is much less prescriptive than Scrum, for instance. In order to provide reassurance, as a coach, you need to trace the questions all the way back to the principles of Kanban, which are grounded in Lean thinking.By listing the 5 most common arguments against Kanban and my response to them, I hope to help people in their Kanban journey and build great organizations that create amazing products.
These answers are based on my own perspective and experience. It would be great to hear your answers and improve the book while more people are introduced to Kanban. The goal is not to explain Kanban scientifically, but provide insights why these arguments don't stand, in a language that is understandable by all.
- 1 What is Kanban?
- 2 We lose our ability to plan
- 2.1 Release planning
- 2.2 Re-planning
- 2.3 Summary
- 3 It will take longer
- 3.1 Parkinson’s law
- 3.2 A healthy balance in Kanban
- 3.3 Theory of constraints for process improvement
- 3.4 Flow
- 3.5 One continuous sprint
- 3.6 Summary
- 4 Things will get stuck, we can’t keep WIP limits
- 4.1 End to end flow efficiency
- 4.2 WIP limits will always cause bottlenecks
- 4.3 Collaboration - daily stand-up
- 4.4 Summary
- 5 Stakeholders don’t care about feeding the flow
- 5.1 Ordering triggers business value
- 5.2 Building an MVP
- 5.3 Stakeholder collaboration
- 5.4 Expectation management
- 5.5 Summary
- 6 We will lose team cohesion
- 6.1 Tearing down walls
- 6.2 Finding a bigger purpose
- 6.3 Creative thinking
- 6.4 Participatory decision making
- 6.5 Achievable goals
- 6.6 Summary
- 7 Summary
- 8 Extras
- 9 Software development is not manufacturing
- 9.1 Support teams
- 9.2 Development teams
- 9.3 Summary
- 10 Bibliography
The Leanpub 60-day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $12 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.