- Paperback: 86 pages
- Publisher: Provoking Thoughts (October 1, 2012)
- Language: English
- ISBN-10: 0955683645
- ISBN-13: 978-0955683640
- Product Dimensions: 8.5 x 0.2 x 8.5 inches
- Shipping Weight: 6.4 ounces (View shipping rates and policies)
- Average Customer Review: 110 customer reviews
- Amazon Best Sellers Rank: #137,490 in Books (See Top 100 in Books)
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.
Other Sellers on Amazon
+ $3.99 shipping
+ $3.99 shipping
+ Free Shipping
Impact Mapping: Making a Big Impact with Software Products and Projects Paperback – October 1, 2012
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
If you buy a new print edition of this book (or purchased one in the past), you can buy the Kindle edition for only $0.99 (Save 90%). Print edition purchase must be sold by Amazon. Learn more.
For thousands of qualifying books, your past, present, and future print-edition purchases now lets you buy the Kindle edition for $2.99 or less. (Textbooks available for $9.99 or less.)
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
In this short book, Gojko describes the tool, why it works, how to use it, how not to use it, and then he kindly walks you through the entire agenda for an impact mapping meeting, explaining how to conduct the meeting and what to expect from each step.
There's no fluff here, just clear instructions on how to use this powerful tool for getting the best results from your product development effort.
I highly recommend it.
Impact maps serve to align teams to business objectives, test mutual understanding of goals and expected outcomes, focus teams toward the highest value features to deliver, and enable collaborative decision-making. As such, impact maps--succinctly and approachably described in Gojko's book--is a key tool for collaborative strategic planning.
This is a book you can reference with ease as you plan and facilitate workshops (collaborative meetings with clear purpose and outcomes) for example: release or iteration planning, product roadmapping, process improvement, product and team chartering. And don't forget: it's not just for software products. You will find impact mapping and Gojko's book, useful for strategic alignment needed for any product--software, systems, or services.
Gojko's book is useful, useable and desirable--all the characteristics we want in a great resource! It is useful for building a shared understanding of the big "why's" for our work that is visual, fast to use, and encourages product partners to collaborate. It is useable--easy to read, including engaging cartoons and color, examples, references, and tips. It's desirable to build product that provide impact--aligns to goals and objectives and provide evidence of their value.
Try impact mapping and use Gojko's marvelous book, Impact Mapping: Making a Big Impact with Software Products and Projects to guide you to do your best, most impactful work.
I gave it 4 stars only because the first 3/4ths of the book were all a bit fluffy, explaining the benefits and methodologies applied in great detail without explaining how or what you do in impact mapping. The last quarter really spelled out the info you needed.
I would have preferred the ratio reversed - there were many questions and more details I would like to learn without picking up another book. Luckily the writer cited plenty of material for me to begin exploring!
Glad I read this - I really needed a tool like this for my current project at work.
I would recommend it to everyone interested in agile management practices. This should not be restricted to managers. Engineers might find the book useful as well because everyone should make good decisions on the scope of an agile product, especially in small teams.
I assume the technique should be usable in many areas, not just software. I don't see anything software-specific in the book. Any goal oriented business following agile management approach should find impact mapping useful.
Most recent customer reviews
Light reading with useful and illustrative examples.
Have gained some takeaways and do recommend to skim it.