- Format: Kindle Edition
- File Size: 3224 KB
- Print Length: 86 pages
- Simultaneous Device Usage: Unlimited
- Publisher: Provoking Thoughts (1 Oct. 2012)
- Sold by: Amazon Media EU S.à r.l.
- Language: English
- ASIN: B009KWDKVA
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Average Customer Review: 54 customer reviews
- Amazon Bestsellers Rank: #52,020 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
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.
|Print List Price:||£14.99|
Save £7.57 (51%)
Impact Mapping: Making a big impact with software products and projects Kindle Edition
|New from||Used from|
Customers who bought this item also bought
Would you like to tell us about a lower price?
What other items do customers buy after viewing this item?
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
This book reminds me so much of Dialogue Mapping: Building Shared Understanding of Wicked Problems. That is also a visual mapping technique serving to surface all private (or hidden) agendas and resolve 'wicked problems'.
I think Impact Mapping (and Effect Mapping) are part of the practises described here Visualising Argumentation: Software Tools for Collaborative and Educational Sense-making.
This book is a much better option. It is more accessible as it uses mind mapping techniques that many people will know. Worth reading several times and trying out the next time you get a stakeholder prepared to spend some time with you.
My only concern is all of these mapping techniques encourage people to think of every concept. It's part of the innate 'once through' mentality. Mapping sessions should be an iterated activity. In my experience repeating things like this (and project planning) never happens. So they become the Big Modelling Up Front anti-pattern.
I would particularly recommend this book to Product Owners/Managers looking at the best way to ensure products address real business objectives.
I rated this as a 4 because while the examples were simple and easy to follow I would have liked at least one more that was a bit more complex .
Impact Mapping is a tool that is intended to help organisations to utilise 'Agile' principles throughout software development organisations rather than localising these changes within Tech Departments. It is intended to help clarify thinking in such a way as to allow organisations to derive project scope from their goals.
I've yet to try the technique of Impact Mapping but I have been persuaded by the argument for deriving product design and features from the desired effects and impacts that a software development organisation wants to have, rather than (as I am more used to seeing) from a set of desired features or features derived from perceived user needs.
The change in thinking required to use Impact Mapping, or any other tool with similar intentions, must in my opinion require many decision-makers to reach the conclusion to work in this way. As a lone voice in a crowd, seeking change, I suspect I require my boss and my boss' boss to consider these ideas.
Which leaves me with the troubling question, how do I encourage others to read it?
For more on the technique itself which is a useful way to generate ideas for features that are firmly oriented to business value (the opposite of just 'doing them because we can'), see Gojko's website at impactmapping.org
What I specifically appreciated about the book was:
- it's short - long enough to cover the ideas in good detail, but with no bloat (300 page textbooks that include 30 pages worth of value are a bane!)
- useful tips on how to apply the technique in different contexts
- draws on and references a lot of the best thinking and best practices in agile product development in general so it's a v useful starting point for further reading.
- clear and jargon-free
In general I think impact mapping is a hugely useful addition to your portfolio of techniques if you're doing agile / startup product development and if you're going to do it you should really get this book.
Would you like to see more reviews about this item?
Most recent customer reviews