Impact Mapping: Making a big impact with software products and projects

I read Goiko Adzic’s book Impact Mapping. After the first reading, I decided that talking about this book was too loud:) In this brochure on 80 The author talks about his approach, based on the idea of which is to visualize the boundaries of the project and the main hypotheses created by the joint efforts of technical and business teams. In fact, these results appear with a consistent response to the questions:

1. Why (Why?) What is the purpose of the whole event - why do we do it?
2. Who (Whoa) - who are the actors (Who is able to produce an effect, who is the consumer)
3. How (How) - examples of influences - in fact, how stakeholders will be affected (How they can help achieve goals, how changes will happen)
4. What (What?) - what exactly do we do?) This is the scope of the project. (playlist)

As a result, we have a mind map with the goals of our project / product describing their impact, which will allow business to consciously approach the achievement of goals. The approach itself is quite obvious in our time, but can be useful if used methodically. If we talk about the brochure, then the positive aspects should be noted:

• its brevity A large number of references to interesting books
• easy to read text
• understandable examples
• the presence of irony, for example, in the description of standard errors when using the approach: astronaut, surrealist, dreamer, robot, octopus, optimist, ...
• Honesty - which is noticeable in the second attached photo, where the businessman asks the consultant "Wait." What's next?" and the consultant replies, "I'm getting off this floor. Your journey continues.” Very typical situation with the involvement of consultants:))

A little more about the approach can be learned from Video from Italian Agile Days 2016 or writer

#Software #SoftwareDevelopment #Management #Processes