Provoking Thoughts Impact Mapping: Making a Big Impact with Software Products and Projects

This book is indeed something which helps in your software/product journey. This book is not just to read but read, practice and re read. Use the references given in the book that's another good read step.Must invest book for Software Product Owners dealing with business side and POs in Software development firms too.

J'ai été très surpris par la taille du livre pour le prix annoncé (73 pages), mais après lecture, il a changé ma vie professionnelle à tout jamais, donc il est parfait :)Si comme moi, vous n'avez pas ou peu d'affinités chef/gestion de projet, mais que vous travaillez sur des projets lean/agiles/... à moyen/long terme, après avoir lu ce livre, vous ne pourrez plus vous passez de cette méthode.

Impact Mapping is an extremely helpful yet (kind of) simple method to explore options on a high level perspective and support decision making. It will help you keep a big picture (of your project or product development) in mind, while making rational decisions and planning experiments in order to get the biggest/fastest business value. It is rare that I want to post every second sentence of a book on our internal company newsletter. A must read for managers, agilists and decision makers.

Impact Mapping provides essential guidance on using an efficient and effective technique that encourages product partners to build the right products--ones that have impact. Impact mapping, the subject of Gojko's lithe, approachable book, is an adaption of visual mapping technique (effect mapping).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.

In many companies, the gap between business people and development team is pretty huge.- Dev teams are working using a water-scrum-fall methodology. This means that only the development teams are agile while the business is still working old school style.- Dev teams and business should communicate really more.- Communication is often a document-based communication. Business and dev teams are “sharing” information only via specifications documents- Dev teams are not aware of the real business goal behind a not-that-well-written user story; they do not know what kind of business value (impact) their development would bring.- Dev teams and business are even not speaking the same language!- …This book will give you the right tool to solve all this.Impact mapping will get business and technical people together. They will share goals. They will share and agree on what are the different options that would reach the goals. Business and technical people will build the map together, having the same objectives in mind, sharing the same vocabulary. Even user stories will be tied to the impact map, using the same actors, impacts and deliverables. This will obviously bring agility into business team as switching to one branch to another if the first choice doesn’t match the measured goal, requires a short feedback loop.Thank you Gojko for having gathered all those great ideas within that short, useful, practical, reference book!