3. Impact Mapping
"strategic planning technique
that prevents organisations from getting lost while building products...by clearly
communicating assumptions, helping
teams align their activities with overall business objectives”
(http://www.impactmapping.org/)
Saturday, 5 December 15
7. The What, not the How
“When it gets dark, I turn on a light.
I can work, cook, read—long after sundown...The simple flip of a switch makes many
things possible and solves many problems.
When I ask developers and engineering managers what their software product
does, often, they don’t tell me.They regale me details equivalent to explaining the
production of electricity, starting from mining coal until the switch closes a circuit.
It’s all about the technical how.
Your customers...want to know the what—what is possible on their side of the
metaphorical light switch when they use your product.”
(http://www.estherderby.com/2015/11/what-does-your-product-do.html)
Saturday, 5 December 15
10. Impact Maps
• Key proponent Gojko Adjic
• Multi-level mindmaps centred on a business
goal
Saturday, 5 December 15
11. Impact Maps
• Key proponent Gojko Adjic
• Multi-level mindmaps centred on a business
goal
• Enable us to map scope from these goals
Saturday, 5 December 15
12. Impact Maps
• Key proponent Gojko Adjic
• Multi-level mindmaps centred on a business
goal
• Enable us to map scope from these goals
• It’s a living, collaborative document
Saturday, 5 December 15
13. Impact Maps
• Key proponent Gojko Adjic
• Multi-level mindmaps centred on a business
goal
• Enable us to map scope from these goals
• It’s a living, collaborative document
• Ties in with aspects of DDD, Lean,Agile
Saturday, 5 December 15
16. Goal (SMART)
• Focus on the problem, not a solution
• Focus on why it’s a useful thing to build
Saturday, 5 December 15
17. Goal (SMART)
• Focus on the problem, not a solution
• Focus on why it’s a useful thing to build
• Make It SMART
Saturday, 5 December 15
18. Goal (SMART)
• Focus on the problem, not a solution
• Focus on why it’s a useful thing to build
• Make It SMART
• “Increase User Logins” :(
Saturday, 5 December 15
19. Goal (SMART)
• Focus on the problem, not a solution
• Focus on why it’s a useful thing to build
• Make It SMART
• “Increase User Logins” :(
• “Increase User Logins from mobile devices
by 25% by March 2016” :)
Saturday, 5 December 15
27. Effects/Impacts
• The change in behaviour of the user.
• Describe the change, not the solution -
what we want them to do, not how they do
it.
Saturday, 5 December 15
28. Effects/Impacts
• The change in behaviour of the user.
• Describe the change, not the solution -
what we want them to do, not how they do
it.
• eg “Make it easier to login” rather than
“Implement FB login”
Saturday, 5 December 15
40. How Do We Know
When We’re Done?
Saturday, 5 December 15
41. How Do We Know
When We’re Done?
• Do the ‘cheapest’ thing
Saturday, 5 December 15
42. How Do We Know
When We’re Done?
• Do the ‘cheapest’ thing
• Measure against our Goal
Saturday, 5 December 15
43. How Do We Know
When We’re Done?
• Do the ‘cheapest’ thing
• Measure against our Goal
• Learn
Saturday, 5 December 15
44. How Do We Know
When We’re Done?
• Do the ‘cheapest’ thing
• Measure against our Goal
• Learn
• Dynamically adjust requirements based on
learnings
Saturday, 5 December 15
45. How Do We Know
When We’re Done?
• Do the ‘cheapest’ thing
• Measure against our Goal
• Learn
• Dynamically adjust requirements based on
learnings
• Don’t spend more than you need to
Saturday, 5 December 15
48. Benefits
• Derive Scope From Goals
• Visual Representation of the product
Saturday, 5 December 15
49. Benefits
• Derive Scope From Goals
• Visual Representation of the product
• Promotes Collaborative working
Saturday, 5 December 15
50. Benefits
• Derive Scope From Goals
• Visual Representation of the product
• Promotes Collaborative working
• Promotes Iterative Delivery
Saturday, 5 December 15
51. Benefits
• Derive Scope From Goals
• Visual Representation of the product
• Promotes Collaborative working
• Promotes Iterative Delivery
• Reduces Waste
Saturday, 5 December 15
54. Other benefits...
• Fixes “As a user syndrome”
• Fixes “As a system syndrome”
Saturday, 5 December 15
55. Other benefits...
• Fixes “As a user syndrome”
• Fixes “As a system syndrome”
• Fixes “Backlog hell”
Saturday, 5 December 15
56. Other benefits...
• Fixes “As a user syndrome”
• Fixes “As a system syndrome”
• Fixes “Backlog hell”
• Stops pollution of the solution space
Saturday, 5 December 15
57. Other benefits...
• Fixes “As a user syndrome”
• Fixes “As a system syndrome”
• Fixes “Backlog hell”
• Stops pollution of the solution space
• “In order to” rationale for each card
Saturday, 5 December 15
58. Other benefits...
• Fixes “As a user syndrome”
• Fixes “As a system syndrome”
• Fixes “Backlog hell”
• Stops pollution of the solution space
• “In order to” rationale for each card
• Visualise and adapt to scope creep
Saturday, 5 December 15
