The document discusses the concept of impact mapping, a strategic planning technique aimed at aligning a team's activities with business objectives while preventing confusion during product development. It highlights various workshops that help clarify goals, impacts, and deliverables, ultimately leading to a consensus on an agreed approach for project delivery. The overall aim is to foster collaboration among executives and teams to enhance agile practices in large corporate settings.

1. Em Campbell-Pretty
Partner, Context Matters
@PrettyAgile
prettyagile.com
em@contextmatters.com.au
Mark Richards
Partner, Context Matters
@MarkAtScale
agilenotanarchy.com
mark@contextmatters.com.au
Bringing Execs to the
Collaboration Table with
Impact Mapping
10Stories Meetup
22nd May 2014

2. HOW I DISCOVERED
IMPACT MAPPING

3. February 2013
How much for…

4. March 2013
What about if we add…

5. April 2013
How about this BRD…

6. May 2013
We only get one chance…

7. June 2013
You need to accelerate delivery!

8. July 2013
Let’s have a workshop!

9. EM:
WHAT DO YOU
MEAN THERE ARE
NO BUSINESS
PEOPLE?!?

10. August 2013
What do you mean you won’t
deliver everything in FY14?

11. September 2013
Here is the list of priorities…

12. October 2013
But you still aren’t going to
deliver everything in FY14

13. WAYNE:
LET ME TELL YOU
ABOUT IMPACT
MAPPING….

15. WHAT IS IMPACT MAPPING?
“Impact Mapping is a strategic planning
technique. It prevents organisations from getting
lost while building products and delivery projects,
by clearly communicating assumptions, helping
teams align their activities with overall business
objectives…”
-Gojko Adzic

16. Source: http://impactmapping.org/drawing.php

18. November 2013
Workshop #1: The Goal

19. THE GOAL: Why are we doing this?
Very few people working on delivery know the
actual expect business outcome.
Knowing why we’re doing something is the key to
making good decisions about cost, scope and
timelines…

20. GOOD GOALS ARE S.M.A.R.T.
Specific
Measurable
Action-Oriented
Realistic
Timely

23. PIXAR PITCH
• Once upon a time there was ___.
• Every day, ___.
• One day ___.
• Because of that, ___.
• Because of that, ___.
• “ ”
• “ ”
• Until finally ___.
• And ever since then ___.

24. ACTORS: Whose behavior do we want to impact?

25. FOCUSING IN

26. December 2013
Workshop #2: Impacts

27. IMPACTS: How should the actors behavior change?

29. January 2014
Workshop #3: Deliverables

30. Deliverables: What can we do to support the impacts?

31. GETTING TO A PLAN

32. February 2014
Workshop #4: Consensus

33. PRESENTING OPTIONS

34. April 2014
The Result?

35. • An agreed approach
• A plan to get there
• While still not smooth sailing …
…the users are happy!
THE RESULT?

36. One more example…

37. AN EXAMPLE

38. TESTING ASSUMPTIONS

39. Now it is your turn…

40. THE GOAL:
To create a Community
that shares about how to
make agile work in big
corporates

41. Em Campbell-Pretty
Partner, Context Matters
@PrettyAgile
www.prettyagile.com
em@contextmatters.com.au
au.linkedin.com/in/ejcampbellpretty/
QUESTIONS?
Mark Richards
Partner, Context Matters
@MarkAtScale
agilenotanarchy.com
mark@contextmatters.com.au