Bringing Execs to the Collaboration Table with Impact Mapping

3,156 views

Published on

Presentation to 10Stories Meetup in Melbourne on 22nd May 2014.

When scaling agile within the enterprise, managing the competing priorities of senior stakeholders is often a challenge. Each stakeholder has their own agenda and determining the right thing for the organisation can be near impossible.

The thought of using many of our classic “agile facilitation techniques” with a room full of executives is enough to send many running for the hills. But the reality is, in the enterprise we need tools that inspire a collaborative mindset at all levels - it’s just not enough for the “teams to work differently”

Impact Mapping is a facilitation technique that brings technologists and senior stakeholders together to meaningfully to explore options. It exposes assumptions and helps shape a path from "We want everything" to "We want to to make these impacts in this order" avoiding the trap of "solutions looking for problems”. Impact Maps visualise “delivery scope in a way that is easy to evolve, reprioritise, grow and shrink as necessary to react to changed market opportunities or new knowledge.” (Gojko Adzic)

In particular, it engages the real decision makers in a collaborative style in short workshops that shape the path, providing the direction and validation required to then transition into the more low-level story based inception work.

In this session Em Campbell-Pretty and Mark Richards from Context Matters will provide an overview of how to create an Impact Map, share some real world examples of how impact mapping has helped support the delivery of software products and provide an opportunity for the audience to start using the tool!

Published in: Business, Technology

Bringing Execs to the Collaboration Table with Impact Mapping

  1. 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. 2. HOW I DISCOVERED IMPACT MAPPING
  3. 3. February 2013 How much for…
  4. 4. March 2013 What about if we add…
  5. 5. April 2013 How about this BRD…
  6. 6. May 2013 We only get one chance…
  7. 7. June 2013 You need to accelerate delivery!
  8. 8. July 2013 Let’s have a workshop!
  9. 9. EM: WHAT DO YOU MEAN THERE ARE NO BUSINESS PEOPLE?!?
  10. 10. August 2013 What do you mean you won’t deliver everything in FY14?
  11. 11. September 2013 Here is the list of priorities…
  12. 12. October 2013 But you still aren’t going to deliver everything in FY14
  13. 13. WAYNE: LET ME TELL YOU ABOUT IMPACT MAPPING….
  14. 14. 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
  15. 15. Source: http://impactmapping.org/drawing.php
  16. 16. November 2013 Workshop #1: The Goal
  17. 17. 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…
  18. 18. GOOD GOALS ARE S.M.A.R.T. Specific Measurable Action-Oriented Realistic Timely
  19. 19. PIXAR PITCH •  Once upon a time there was ___. •  Every day, ___. •  One day ___. •  Because of that, ___. •  Because of that, ___. •  “ ” •  “ ” •  Until finally ___. •  And ever since then ___.
  20. 20. ACTORS: Whose behavior do we want to impact?
  21. 21. FOCUSING IN
  22. 22. December 2013 Workshop #2: Impacts
  23. 23. IMPACTS: How should the actors behavior change?
  24. 24. January 2014 Workshop #3: Deliverables
  25. 25. Deliverables: What can we do to support the impacts?
  26. 26. GETTING TO A PLAN
  27. 27. February 2014 Workshop #4: Consensus
  28. 28. PRESENTING OPTIONS
  29. 29. April 2014 The Result?
  30. 30. •  An agreed approach •  A plan to get there •  While still not smooth sailing … …the users are happy! THE RESULT?
  31. 31. One more example…
  32. 32. AN EXAMPLE
  33. 33. TESTING ASSUMPTIONS
  34. 34. Now it is your turn…
  35. 35. THE GOAL: To create a Community that shares about how to make agile work in big corporates
  36. 36. 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

×