Impact Mapping
About this book
Adzic's short book on a visual technique linking deliverables back to goals. The map has four levels asking why, who, how and what, so every feature traces to an actor whose behaviour must change in service of a measurable goal. Covers running a mapping session, using the map to decide what not to build, and treating branches as assumptions to be tested. Around eighty pages and mostly worked examples.
Description via Product Digest.
Topics
Related concepts
- Requirements and use scenariosRequirements articulate personas and their problems so the right thing gets built. A use scenario puts the problem in a story so the context travels with it.
- Outcome and outputOutput is what the team produced. Outcome is what changed for someone because of it. A product owner is accountable for the second and is usually measured on the first.
- Product roadmap and release planThe roadmap shows the vision and the phases of deliverables and is a plan rather than a commitment. The release plan is the dated one. Keeping them separate is what stops a direction becoming a promise.