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
+ $3.99 shipping
Impact Mapping: Making a Big Impact with Software Products and Projects Paperback – October 1, 2012
"Children of Blood and Bone"
Tomi Adeyemi conjures a stunning world of dark magic and danger in her West African-inspired fantasy debut. Learn more
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
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 89%). 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.)
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
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.
Good focus on keeping things simple and eliminating waste (well, forward by Tom Poppendieck, so I guess that makes sense!).
One thing that I really liked was the discussion of abstracting scope away until we are ready to do something. Instead of prioritizing among a list of stories, Gojko suggests prioritizing the business goals (prioritize between all the different impacts we want to achieve on the behavior of specific actors, and early on, don't focus as much on how we intend to achieve an impact). I think there is a lot of value in that -- lists of story cards are waste, and can change frequently, and he instead focuses on the big picture, which is the high-level business goals, and we prioritize based on that. (The stories live under the business goals, but Gojko argues that there's no point in talking about a story for anything other than our highest immediate goals.)
There is a section about how impact mapping is a very useful way to run a meeting, and it makes a lot of sense as to how this can help promote useful collaboration around a common goal.
I also really like that Gojko suggests not wasting time on estimating cost and time, and instead focus on value and return on investment. There is a good discussion on how budget and estimation should not be big-bang events.
And there's no fluff. The book is short, but very useful and to-the-point. Highly recommend!
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.