So I have to admit – I expected more from this book. It’s been lauded as an important part of the Agile “Body of Knowledge” and I probably expected to much – especially in the context of why I read the book recently.
So what didn’t I like? First, the language of the book wasn’t easy to absorb. Some people can write so well, it’s easy to take in. Others (myself included) are more heavy-handed it makes reading more of a chore. Second – the advice in the book is very focused on quickly iterating through prototypes and MVPs. It doesn’t suit the character of the initiative I’m working on now (luckily there’s also 4DX). But that’s not the author’s fault.
Having said these negatives, I believe the book as a place in the Agile canon and definitely should be read by Agile practitioners – even if it doesn’t directly suit your needs.
Agile Musings 