Impact Mapping practice
Gojko Adzic refined and developed the practice of collecting primary requirements called Impact Mapping. Its essence is to build cause-and-effect links (Traces) from business goals to specific automation elements (product functions). The developer, together with the customer, must answer the following questions:
- Why do we need a particular piece of functionality, and which measurable goal do we want to achieve? These are our future business goals.
- Who is involved in achieving this goal? These are the actors: employees, people, departments, or units.
- How does this person or employee achieve the goal, and what work do they perform? This is the impact the actor has on achieving the goal.
- What does this person need from the software system in order to do their work? These are specific features or product functions (large Stories) that the actor uses to influence the goal.
You can visualize these links with a marker and the "mind map" technique, or with sticky notes.
When the map is complete and the customer and the developer have agreed on the goals and the scope of work, the results can be recorded in the "Features" module, for example as follows:
