Impact Mapping: Making an Impact over Shipping Software
59
Em Campbell-Pretty Partner, Context Matters @PrettyAgile www.prettyagile.com au.linkedin.com/in/ejcampbellpretty/ [email protected] Impact Mapping: Making an Impact over Shipping Software Agile Australia 18 th June 2014
-
Upload
em-campbell-pretty -
Category
Software
-
view
1.152 -
download
1
description
Are you lost in a sea of business requirements? Are you struggling to articulate the business value of your technology project? Do your user stories lack context? Is there a lack of alignment between your delivery teams and business stakeholders? If you answered yes to one or more of these questions then this session is for you! Impact Mapping is a facilitation technique that brings technologists and senior stakeholders together 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. This session provides 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 even provide an opportunity for you to start using the tool! Presented at Agile Australia 2014
Transcript of Impact Mapping: Making an Impact over Shipping Software
Em Campbell-Pretty Partner, Context Matters @PrettyAgile www.prettyagile.com au.linkedin.com/in/ejcampbellpretty/ [email protected]
Impact Mapping: Making an Impact over Shipping Software
Agile Australia 18th June 2014
Build the Right Thing Vs.
Build the Thing Right
“There is surely nothing quite so useless as doing with great efficiency what should not be done at all.”
– Peter Drucker
Impact Mapping is a strategic planning technique. It prevents organisations from getting lost while building products and delivering projects…
- Gojko Adzic
HOW I DISCOVERED IMPACT MAPPING
February 2013
Can you help?
March 2013
Who is the Product Owner?
April 2013
How do we expedite delivery?
May 2013
Here is the BRD….
June 2013
Can we report data that has been deleted by robots?
July 2013
You need to accelerate delivery!
August 2013
What do you mean you won’t deliver everything in FY14?
September 2013
Here is the list of priorities, we added a few extra features…
October 2013
Has anyone seen the PO?
Source: https://www.flickr.com/photos/trancemist/361935363/
WAYNE: LET ME TELL YOU ABOUT IMPACT MAPPING….
November 2013
Workshop #1
SETTING THE STAGE
THE GOAL:
Why are we doing this?
Source: http://gojko.net/2013/02/13/the-february-revolution/
• Why are we doing this?
GETTING TO THE GOAL – ASK:
• Identify why the product will be useful • Explore the problem to be solve
GETTING TO THE GOAL- DO:
• Define the scope • Provide the solution
GETTING TO THE GOAL- DON’T
GOOD GOALS ARE S.M.A.R.T.
Specific Measurable Action-Oriented Realistic Timely
PIXAR PITCH
• Once upon a time there was ___. • Every day, ___. • One day ___. • Because of that, ___. • Because of that, ___. • “ “ “ • “ “ “ • Until finally ___. • And ever since then ___.
http://www.prettyagile.com/2014/06/pitching-pixar-pitch.html
THE ACTORS:
Who can effect the outcome?
• Who can produce the desired effect? • Who can obstruct it? • Who are the consumers or users of our product? • Who will be impacted by it?
GETTING TO THE ACTORS – ASK:
• Identify who will derive value • Consider
– Primary Actors whose goals are fulfilled – Secondary Actions who provide services – Off stage actors, who have influence but do not benefit
or provide services
• Be specific
GETTING TO THE ACTORS – DO:
BRAINSTORMING ACTORS
FOCUSING IN
December 2013
Workshop #2
THE IMPACTS:
How should our actors’ behavior change?
• How should our actors’ behavior change? • How can they help us to achieve the goal? • How they can obstruct or prevent us from
succeeding?
GETTING TO THE IMPACTS - ASK:
• Focus on desired changes in business activities • Show how the activity is different to what is
currently possible • Consider negatives and positives • Think about multiple impacts per actor
GETTING TO THE IMPACTS – DO:
• Record every possible impact • List software ideas
GETTING TO THE IMPACTS – DON’T:
BRAINSTORMING IMPACTS
THE “GROAN ZONE”
MIND MUP
www.mindmup.com
THE DELIVERABLES:
What can we do to support the desired impacts?
• What can we do, as an organisation or a
delivery team, to support the required impacts?
GETTING TO THE DELIVERABLES – ASK:
• Refine it iteratively as you deliver. • Treat deliverables as options. • List only high level deliverables. • Consider anything that helps achieve the
impact
GETTING TO THE DELIVERABLES – DO:
• Try and make it complete from the start. • Take it for granted that everything listed
will be delivered. • Don’t get into the details. • Limit solutions to software
GETTING TO THE DELIVERABLES – DON’T:
January 2014
Workshop #3
PLAYING BACK THE IMPACT MAP
GETTING TO A RELEASE PLAN
February 2014
Workshop #4
REACHING CONSENSUS
April 2014
The Result
• An agreed set of priorities
• An iterative plan to get there
• While still not smooth sailing …
…the users are happy!
THE RESULT?
An example from Facebook (via Gojko)
AN EXAMPLE FROM GOJKO…
TESTING ASSUMPTIONS
USER STORIES FIT ON IMPACT MAPS
Em Campbell-Pretty Partner, Context Matters @PrettyAgile www.prettyagile.com au.linkedin.com/in/ejcampbellpretty/ [email protected]
WANT TO KNOW MORE?
Read “Impact Mapping” by Gojko Adzic Check out impactmapping.org/ See my blog: bit.ly/PrettyAgileImpactMap
