Warning: This book is not just about Kanban - it goes a lot deeper than that. This is possibly the best text I’ve read at a practices level to implementing Agile methodologies in large/corporate organizations. I wish I had read this book years ago!
In the book ‘Principles of Product Development Flow’, Donald Reinertsen outlined at a principle level the economies of flow. I believe ‘Kanban’ is the practical implementation of Donald Reinertsen’s book.
To give some background - I’ve been involved in large organizations adopting Agile methodologies for several years. I could personally relate to nearly every piece of advice given in this book. There were things I had experienced and figured out already (and Kanban re-affirmed my opinions), or things I was experiencing with teams currently (and Kanban has given me sound advice on how to move forward). Normally, I do an outline of highlights of a book. In this case, it is hard because I found pretty much every page valuable.
Chapter 1 - Solving and Agile Manager’s Dilemma
Read the entire chapter. It frames the current challenges that agile managers face.
Chapter 3 - Recipe for Success
Must read. I came up with something similar to this on my own, but got the order messed up. If I had done it David’s way, I believe I would have had a much better outcome.
- Focus on Quality
- Reduce Work-in-Progress and Deliver Often
- Deliver Often
- Balance Demand against Throughput
- Prioritize
- Attack Sources of Bariability to Improve Predictability
Chapter 19 - Sources of Variability
- p.g. 223 Predictability and risk management typically should trump an opportunity to increase throughput, as business owners and senior managers value predictability more than throughput.
Buy from Amazon
ISBN-13: 978-0984521401
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.
Submit an article or tip
