Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer – no Kindle device required. Learn more
Read instantly on your browser with Kindle Cloud Reader.
Using your mobile phone camera, scan the code below and download the Kindle app.
Enter your mobile phone or email address
By pressing ‘Send link’, you agree to Amazon's Conditions of Use.
You consent to receive an automated text message from or on behalf of Amazon about the Kindle App at your mobile number above. Consent is not a condition of any purchase. Message and data rates may apply.
Follow the Author
Impact Mapping: Making a big impact with software products and projects Kindle Edition
- ASIN : B009KWDKVA
- Publisher : Provoking Thoughts (1 October 2012)
- Language : English
- File size : 2700 KB
- Simultaneous device usage : Unlimited
- Text-to-Speech : Enabled
- Screen Reader : Supported
- Enhanced typesetting : Enabled
- X-Ray : Not Enabled
- Word Wise : Not Enabled
- Print length : 105 pages
- Best Sellers Rank: 117,668 in Kindle Store (See Top 100 in Kindle Store)
- Customer Reviews:
About the author
Review this product
Top review from Australia
There was a problem filtering reviews right now. Please try again later.
Top reviews from other countries
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.
The bit in the book about making tasks measurable, while challenging demonstrates the failing mindset of many ongoing projects.
Refreshing to find a booked that focuses on delivery and not on the waste of governance, e.g. backlog grooming and writing lots of stories. So enjoyed this book!!
So first off, I am very impressed with the way Gojko has synthesised a number of techniques to produce something which quickly extracts the key information from stakeholders, in a workshop environment, with more precision and yet without getting into implementation details. You don't usually get much time to do this sort of thing, so focus an speed are essential.
I have not yet tried this technique myself (but I will!), but there is an interesting vimeo which includes a section by a facilitator from a company using the technique: [...]
So another key point is the amount of background material already available on [...]
The book itself: it is nice and short, with a light writing style, so quick to read. It covers what Impact Maps are, their role and how to create them. I particularly liked the emphasis on pragmatically extracting measurements, plus warning signs for various types of problems such getting the right people, right number of people, facilitating tips, and specific mapping gotchas.
This book is well worth the price and the short time you will require to assess the relevance to you - mastering will take longer.
Why not 5-stars? I would have liked a section which took a look at another example in more detail - there is a running example through the text which is good, but an example which was almost a "play through" of a session would have been perfect.
The book addresses a problem any type of project often faces - how to get agreement from stakeholders on what the goals of a project are and what needs to change to achieve it, and avoid jumping straight into a wishlist of features and solutions driven by who shouts the loudest. The technique has the added benefit of keeping the project at a level of definition where solutions can still be negotiated and evolved iteratively, and will help to keep the team focused on meeting the business objectives.
I've also recently read 'Discover to Deliver' (Gottesdiener/Gorman) and can see impact mapping working nicely with the methods described there.
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 .