- File Size: 3224 KB
- Print Length: 86 pages
- Simultaneous Device Usage: Unlimited
- Publisher: Provoking Thoughts (October 1, 2012)
- Publication Date: October 1, 2012
- Sold by: Amazon Digital Services LLC
- Language: English
- ASIN: B009KWDKVA
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Lending: Enabled
Amazon Best Sellers Rank:
#268,805 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
- #64 in Kindle Store > Kindle eBooks > Computers & Technology > Business > Project Management
- #75 in Kindle Store > Kindle eBooks > Computers & Technology > Computer Science > Systems Analysis & Design
- #79 in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Project Management
Impact Mapping: Making a big impact with software products and projects Kindle Edition
|Length: 86 pages||Enhanced Typesetting: Enabled||Page Flip: Enabled|
Matchbook Price: $0.99
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.)
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.
Customers who bought this item also bought
Would you like to tell us about a lower price?
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
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.
Eric Ries' "Lean Startup" is a wonderful book, but it left me wondering how to implement his concepts. This book brought it all together for me -- Agile, Lean and the Lean Startup.
- clearly written
- to the point
- lots of references to additional information (and acknowledgement of other thinkers)
A book is short and light in reading. I think an introduction (selling) part could be shorter and Impact Mapping newbies would expect and benefit from bigger 'how to' part with more examples. It also contains a few 'Don't dos' which helps to avoid wrong practices!
How do I benefit from reading this book? I will definitely try to spread Impact Mapping across our product management team and simply try it out. Maybe you should try it too?
Impact mapping cover this as part of a bigger picture and explains what's this bigger picture, why it does matter, who is this helpful for and how to make it happen. Highly recommended!
I think it's great that this book does not waist time and effort trying to repeat what others already did and is not essential for the reader to know. I know my share of Agile Principles and Management ideas, so I did not miss any details, but I don't think you need to be a Ninja to understand this book. And if your are pussled by anything then the link is right there in the book.
All in all great, short and to the point Thanks Gojko! Let this inspire the many new books.
Most recent customer reviews
Light reading with useful and illustrative examples.
Have gained some takeaways and do recommend to skim it.
As an author myself, I was struck by two things:
First, there...Read more