With the adoption of agile and better engineering techniques we have pretty much solved the problem of “delivering” software. Unfortunately, it’s not enough. Now we need to turn our focus to delivering “the right” software – software that makes an impact to the customer.

The answer to building the right software begins with a better understanding of the business opportunity and goals. Best of all, we can do this using a collection of familiar concepts, combined in a powerful new way, bringing a shared and measurable vision to your scrum project. This approach is called “Impact Mapping.”

This workshop introduces “Impact Mapping” by demonstrating a collaborative approach to solving the challenge of building the right thing. Breaking into small teams, we will build a sample Impact Map, learn to identify and verify the assumptions you've made, and find new approaches to solving the business problem. We will also discuss using this to measure the output of our effort. Attending participants will receive a handout with a worked example and sample questions and techniques that help lead to a successful mapping session.

Don’t miss this opportunity to learn about and practice the techniques to uncover assumptions and motivations about your current project – and ensure your next project makes the right impact on customers and bottom line. Let's help our customers better refine and communicate their goals. Impact Mapping is at the heart of the customer voice because it literally gives voice to their needs. We will see you at IMPACT MAPPING! 


Outline/Structure of the Workshop

The session will start at the point where the customer has identified the value that they want to achieve and their requirements (An output "report").

Step 1 (15 Minutes). The "Impact Map" will be introduced by way of an interactive worked example. This will show the audience how to create a map using a step-by-step identification of the question sets. The process ends when we have a complete map. The questions are:

  1. Why are we doing this? What are the desired business outcomes?
  2. Who are the people who can do this? What is the stakeholder group who we believe can help us achieve the outcome?
  3. How can the group contribute or obstruct the goal? What about the stakeholder needs help or hinder the desired outcome?
  4. What are the activities or software capabilities that would support the stakeholder needs in contributing to our business goal? What are the features, or what can we do to support the stakeholders in supporting the business goal?

One or more versions of the map and questions will be posted as cheat sheet to the audience.

Step 2 (45 Minutes) The audience will then break into smaller groups and work on an example of their own through a guided exercise.They can either provide an example from their place of work, or we will provide them with examples.

Step 4 (15 minutes). 3 groups (or more if time permits) shares their experience.

Step 5 (15 minutes). Feedback, learning, and questions from the audience

“Impact Mapping” is also the title of a brief book, published by Gojko Adzic in November, 2012. The workshop facilitator worked with the Gojko in the development of this presentation.

Learning Outcome

  1. Learn the value and structure of an Impact Map
  2. Practice with facilitating the Impact Map exercise, uncovering project motivations

Target Audience

Product Owners, Business Analysts, Business Partners


schedule Submitted 6 years ago

  • Sue Johnston

    Sue Johnston - Think "renovation" not "transformation"

    45 Mins

    If you've ever been through a home renovation, you know what a massive disruption it can be. Dust is everywhere, your mid-day quiet coffee ritual is displaced with the sweet sounds of hammer-to-nails and saw-to-wood and some (or all?) of your house is pretty much unusable.

    When Agile Transformation is used as a trigger for change, it's going to render some parts of your organization unusable until some progress is made.

    In a reno, we tolerate the upheaval and turmoil because we know that, when it's done, we'll have a better place to live.

    In this session, with help from Sue Johnston, Jason Little and Andrew Annett, you'll learn to apply the metaphor of Organizational Remodelling to implementing and guiding change in your organizations.

  • Jeffrey Davidson

    Jeffrey Davidson - Writing Better User Stories

    60 Mins

    "As a user of your system, I want functionality so that I can achieve my goals. Unfortunately, your team's users stories are getting in the way."

    Users Stories, the tool teams use to break ideas into small chunks of deliverable work, are easy to describe and challenging to write. This session is about writing great user stories and acceptance criteria by ensuring everyone on the team knows what needs to be done. We will discuss what elements should be included and which ones are optional; why the size of your user story is important and how to make them smaller; and the structure for better acceptance criteria.

  • Jason Little

    Jason Little / April Jefferson - Creating Alignment for Agile Change

    60 Mins

    Sometimes people in organizations feel as though Agile has been pushed on them. They end up going through the motions, without any real sense of ownership of what they are doing. Instead of actually implementing meaningful changes, organizations end up doing "Agile in name only" by slapping Agile labels on existing processes. Then Agile is blamed for "not working". This isn't an Agile problem. It's an alignment and ownership problem. In this session, through theory and multiple real-world case studies, you'll learn how to co-create change by involving the people affected by the change in the design of the change.


  • Guy Royse
    Guy Royse
    Pillar Technology
    schedule 6 years ago
    Sold Out!
    240 Mins

    Are you tired of TDD workshops that make you do boring things like calculate bowling scores and prime factors or demonstrate how to win at the game of life? If so, this is the session for you In this TDD workshop we will be building the domain model for EverCraft -- a new MMORPG from Blizzards of the Coast. We have lots of story cards prepared covering features from combat to magic, classes to spells, and races to items. Plus, we'll be defining some of these cards during the session in case you want that +9 knife of ogre slaying or enjoy casting magic missile at the darkness.

    This workshop is language agnotisic and for all levels of developers. The focus is on TDD and emergent design but pair programming will be covered as well. The only requirement is that you bring a laptop and that you be able to test-drive you code with your language of choice. When you are done you will emerge a better programmer for the experience but there is small chance you will have a craving for Cheetos and Mountain Dew.

  • 90 Mins

    What does it mean to build antifragile relationships and teams? Teams and organizations, at least successful ones, are based on relationships that "work." Often we say we want 'strong' or 'good' relationships, but is 'strong' good enough? We will look at ways you can identify if the foundation of your team relationship is fragile or antifragile. Then we will work with a number of approaches and tools to help you create or expand on the foundation of an antifragile for your team.  

    Help your team (or organization) move towards a space where your relationships and therefore teams can thrive. We will consider how to build an alliance with a team and how to setup, in advance, to deal with potential conflicts. We will also explore a number of common issues contributing to toxic team situations. Antifragile is not an endpoint.  Like agile, it is a journey and mindset. The ideas we will explore are not just about "them", but are about "us" first. We have to start with us. What can WE bring to the table and what can WE do or be. Expect to work individually and with others in this interactive workshop.

  • Diane Zajac

    Diane Zajac - There’s No “I” in Team, But Should There Be?

    90 Mins

    Scrum suggests that business analysts, testers and developers shed their old job titles and don the badge of “team member.” And current trends like mob programming further encourage team members to abandon their individual goals in the interest of team achievements. It seems there really is no “I” on some teams...but should there be?

    In this session, Diane evaluates the pros and cons of eliminating job titles and examines the concept of becoming a generalizing specialist. What does that really mean? What are the impacts to the team? Can you maintain your individual skills while your contributions to the team are getting blurred?

    Come and join in the discussion!

  • Matt Barcomb

    Matt Barcomb / Matt Barcomb / Rachel Howard - Talent Development 3.0

    45 Mins

    Your company’s lean/agile transformation needs to include a major overhaul of your talent development practices. The landscape of finding, growing and retaining talented people has changed drastically over the last 10 years and lean practices and an agile mindset only accelerates that change so you need to be prepared?


    During this session, Rachel Howard and Matt Barcomb will guide you through new ways of finding good people that are better matches for your organization, professionally and culturally as well as more effective ways to grow talent in-house and creative retention methods that better match the needs of the new generation of technologists.


    Anyone who has traditional “HR responsibility” or is involved with traditional recruiting, hiring, compensating or training will leave this session with fresh ideas and pragmatic practices they can put to use quickly.