Escape Velocity: Shifting from Constraint-based to Value-based Delivery through Impact Mapping

How do you measure a project's success?  Traditional project management defines success as delivering the baseline requirements on-time and within cost.  These measures are constraint-based.  Some agile projects define success when the backlog is empty and the burn-down chart has hit zero. I call this measurement, velocity-based. Velocity, when used to measure success, pulls us back into the gravity well of constraint-based measurements.   Is there a better way? Can we escape velocity? Shouldn't we measure the success of a project based on some value delivered to someone?  Such a measure would be value-based. Enter impact mapping, a value-based approach to measuring project success.  This talk is about the impact of impact mapping, why you should use it, and how you can use it to measure a project's success so that you are delivering true value to the end-user and not just a collection of user stories.

 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Discuss constraint-based, velocity-based, and value-based project success measurements 
  • Walk the audience through a simple impact map
  • Highlight the value, measurements, assumptions, metrics, and prioritization map visible through the impact map
  • Discuss how the discussions around the impact map shifts the conversation into the business point of view and towards end-user value
  • Conclude with a short discussion on how value-based lives within the traditional constraints and references for further learning on Impact Mapping.

The presentation is available for viewing at slideshare.net.

Learning Outcome

  • Understand what is impact mapping and, more importantly, the impact of impact mapping
  • Learn a technique that redefines project success in terms of value delivered to someone 

Target Audience

Managers, Business Analysts, and Coaches.

Prerequisite

There are no prerequisites, though reviewing material at impactmapping.org or reading Gojko Adzic's book, Impact Mapping, are helpful either before or after the talk.

schedule Submitted 2 months ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • 45 mins
    Workshop
    Intermediate

    Imagine you were hired to provide consulting assistance for a new team just starting out with Kanban. The team has been struggling with their implementation and is looking forward to your expert guidance, support, and advice. It’s your first day and you just walked into the team room to look at their board. You want to make smart observations and thoughtful interpretations so you can have meaningful conversations with the team members. The team starts assembling in the team room for the daily standup and you plan on making some comments afterwards.

    What comments would you make? What thoughtful questions would you ask?

    This interactive presentation provides a detailed look at how to interpret and thoughtfully observe Kanban Boards to better understand the work of your teams. We will start with an overview of the Lean Kanban Method and then proceed through a series of interactive exercises that give you an opportunity to review and interpret various Kanban boards. The exercises will increase your understanding of Kanban systems and provide opportunities to practice interpreting various board setups so you can have thoughtful and meaningful conversations with your teams.

  • Liked Daniel Davis
    keyboard_arrow_down

    Daniel Davis - So You Want To Go Faster?

    45 mins
    Talk
    Beginner

    How frequently does a good agile team deploy to production? Not every team is capable of deploying "on every commit". What does it take for a team to even start deploying at the end of each sprint, or each week, or each day?

    Most companies don't realize that deploying more frequently often requires both significant technical change as well as cultural change. In this talk, I'll guide you through what it takes to deploy more frequently, both from the technical side of setting up pipelines as well as the organizational side of removing red tape. I'll draw on the unique challenges that teams must overcome at each step of the way, from deploying once a month all the way down to full continuous delivery. If your team has been struggling to go faster, come see how you can change to get there. And if you already are at full continuous delivery, come see how to go even faster than that!

  • Liked Richard Cheng
    keyboard_arrow_down

    Richard Cheng - How do I know if I have the right Product Owner?

    Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 3 days ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Is your Product Owner available to the team, empowered to make decisions, knowledgeable in their business domain, engaged in the product and leading the way for delivery of value? This session does a deep dive in the these ideas.
The session starts with a brief Seinfeld video to demonstrate the importance of Product Ownership. The session then discusses 5 key attributes to look for in a Product Owner:

    1. Bandwidth
    2. Power

    3. Knowledge
    4. Interest
    5. Vision

    After that discussion, we will have an interactive exercise to identify what a Product Owner does day to day. The debrief will identify the balance a Product Owner must have between working with stakeholders, end users, customers AND working with the Scrum team AND product backlog refinement.

    The session concludes with the presenter sharing a Product Owner persona sheet. This persona sheet measures product owners across the 5 attributes mentioned above and presents a narrative on their core strengths and risks.

  • Liked Richard Cheng
    keyboard_arrow_down

    Richard Cheng - Group Hug: Implementing Agile Across Multiple Teams

    Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 3 days ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The patterns for implementing Scrum at the team levels have largely been set, but what about dealing with Agile and Scrum across multiple teams. Is the answer just magical words like scaling, or SAFe, or LeSS? What are the core concepts and successful patterns? Is it just one big group hug?

    In this session, we will explore core concepts around implementing Agile concepts across multiple teams. The session starts with a simulation that explores distributing people across teams (which will actually NOT involve any hugging). From there, this session dives into:

    • Prioritization across multiple teams
    • Product Ownership across multiple teams
    • Dependencies and team alignment
    • Communities of Practice
    • Communication and collaboration across teams
    • The role of managers
    • A quick look at scaling methods

    Coming out of this session, attendees will have an understanding of core concepts and fundamental helpful practices in implementing Agile concepts across multiple teams.

  • Liked Julie Wyman
    keyboard_arrow_down

    Julie Wyman - Multitasking is Evil

    Julie Wyman
    Julie Wyman
    Agile Coach
    Excella Consulting
    schedule 1 week ago
    Sold Out!
    10 mins
    Workshop
    Beginner

    For a long time multitasking has been considered a must-have skill when, in fact, it makes us less productive and more prone to error. But even with plenty of studies and papers supporting that idea, it can be hard to convince managers and stakeholders that we should be taking on less at a time. In this lightning talk, we'll run through one very quick, lightweight simulation (Multitasking is Evil) you can use to help make that case and show that lowering work in progress is the way to go!

  • Liked Jaap Dekkinga,
    keyboard_arrow_down

    Jaap Dekkinga, - Stakeholder involvement (sub title: How do I involve my stakeholders best in an Agile environment?)

    Jaap Dekkinga,
    Jaap Dekkinga,
    Agile coach
    Excella
    schedule 1 week ago
    Sold Out!
    45 mins
    Tutorial
    Beginner

    One of the struggles I have seen when organizations transition to Agile in relation to the Agile principle "Customer Collaboration Over Contract Negotiation" is: When and how do I involve the right customer.

    Goal of this presentation:

    • Provide tools on how to involve different types of stakeholders
    • Tool to identify different types of stakeholders

    In the presentation I will explain the 2 step process of:

    • Step 1: map out the players for a value stream, product, or feature(set) in a simple 2x2 Stakeholders Matrix (influence/power and interest)
    • Step 2: Learn about the tools and techniques to involve players in each quadrant based on their specific strength or opportunity

  • Liked Julie Wyman
    keyboard_arrow_down

    Julie Wyman - Managing Resistance: How the Kanban Method Supports Lasting Change

    45 mins
    Talk
    Beginner

    “Going Agile” is a big cultural change for most organizations and it’s significance, impact, and the effort required for successful implementation can often be underestimated. There are many benefits to be gained by adopting a more Agile approach, including quicker feedback loops, more focus on value, and higher levels of collaboration. However, for Agile to succeed in the long-term it’s essential to set expectations up front and to balance the amount of change with the amount of disruption it will cause. In this session, we will look at how David Anderson intentionally built change management principles into his Kanban Methodology and explore other change management techniques the Agile community can leverage when helping organizations transition to Agile.

  • Liked Brian Sjoberg
    keyboard_arrow_down

    Brian Sjoberg - Understanding the Whole System, Not Just a Part

    45 mins
    Tutorial
    Beginner

    Are your solutions to recurring issues having only minor improvements? Are some of these solutions actually making things worse in the long run? When answering yes to these, typically, we are trying to solve the issues with too narrow a view. Oddly we think we are addressing it at sufficient level but usually not. In order to see the entire picture we need a common language that will enable us to understand an entire complex adaptive system (e.g. organizations, teams, individuals). Join us as we learn a language called System Modeling (aka. Causal Loop Diagrams).

    With this language we will be able to have rich dialogue to gain a full understanding of the entire complex adaptive system so that we can create solutions at the fundamental level and not the symptomatic level. Addressing system issues at the fundamental level will significantly improve the system. Symptomatic solutions may give the appearance of improvement in the short term but typically make things worse in the long run. Unfortunately we usually pick the symptomatic solutions because they seem obvious and we don't realize the long term impacts because of feedback delays that could take weeks, months or even years to realize.

  • Liked Brian Sjoberg
    keyboard_arrow_down

    Brian Sjoberg - Why Are We Going So Slow? ... Time to Get Your Productivity Game On!

    45 mins
    Workshop
    Beginner

    Are you struggling with delivering a potentially releasable working product every iteration? Ever wonder what one of biggest reasons we have difficulty getting things done at the individual, team and organizational level are? Do you keep doing something even though you know it reduces your productivity and lowers quality? We are going to run an exercise that highlights one of the major culprits that you have all experienced and probably continue to experience. The exercise will likely ignite a little (or big) fire in your belly that will help you become more productive and improve the quality of your work. From this, we will discuss ways to improve this at the individual, team and organization levels.

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 1 month ago
    Sold Out!
    45 mins
    Talk
    Advanced

    So you are considering getting a coach to help you in your transition to Agile. Or perhaps you are an Agile practitioner considering becoming an Agile coach. What do these Agile coaches do? What makes them different?

    This session will enter the foyer of the house that describes what coaches do and considerations one can have when they think about coaching (including hiring one). Prepare to be challenged and to learn a bit of what it takes to be or work with a coach; it has little to do with courses or certifications, though they may help. In covering what coaches do, one can now begin to think along the lines of what the skills one may need to improve.

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 2 months ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    Losing good people during your transformation? Getting more resistance than you expected? You may be producing unwanted reactions in the way you are leading your people through change. If you want your Agile transformation firing on all cylinders without the harmful side-effects, people at all levels need to become Catalysts.

    Catalytic leaders help lead continual improvement - change. How can we do that? How can anyone be a leader? This workshop will mix presentation with exercises to help you understand practical things you can do to lead change effectively.

  • Liked Richard Cheng
    keyboard_arrow_down

    Richard Cheng - Story Time - 5 Top Attributes of a Product Owner

    Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 3 days ago
    Sold Out!
    10 mins
    Experience Report
    Intermediate

    In this lightning talk, Richard Cheng will share a story from his Motley Fool days in regards to the 5 things to look for in a Product Owner:

    • Bandwidth
    • Power
    • Knowledge
    • Interest
    • Vision

  • 45 mins
    Talk
    Intermediate

    As we have seen from recent reports in the news and elsewhere, cyberattacks come many sources. How can we use Agile practices to improve organization's information security posture?

    In this session, Dan and Paul will discuss techniques that can help make information security an important part of software development and speed your response to threats. The use of hardening pipelines, dark stories, and user stories/acceptance criteria that map to policy guidance based on NIST 800-53 controls will be discussed and how each approaches improving your security posture from a different angle.

  • Liked Lisa Cooney
    keyboard_arrow_down

    Lisa Cooney - Agile in the Wilderness: How to Succeed When They Can't Spell Scrum

    45 mins
    Experience Report
    Beginner

    In this interactive and informal session, you will hear a story about how Agile led to the successful delivery of a large training program (in a non-IT environment) where Agile was completely unknown and unwelcome. You will learn how the Agile values and principles guided my decisions and behavior and contributed to success. We will discuss what I call "stealth Agile" which is applying the techniques and mindset without using the odd and intimidating vocabulary. You will hear how I implemented Scrum with my own team, but lightweight Agile with a soft touch for my management. Eventually I was able to influence the wider environment, gradually coaching them and teaching them Agile, resulting in a self-sustaining Agile team functioning reasonably well as a pod surrounded by waterfall approaches.

    During this conversational session, you will have the opportunity to ask questions and share your own stories.

  • Liked Daniel Davis
    keyboard_arrow_down

    Daniel Davis - Everything Object Oriented Design Taught Me About Leadership

    45 mins
    Talk
    Beginner

    Most senior software developers eventually find themselves in a position of leadership. About two years ago, I was in the same boat, being asked to take over as tech lead for a large agile project. I felt unprepared, I didn't know the first thing about being in charge! I found myself falling back to the thing I had spent years learning: object-oriented design principles.

    In this talk, I'll walk through some of the parallels between clean coding and leadership. I'll discuss some design anti-patterns with different styles of leadership and how to avoid falling into classic management traps. If you've always felt like your bosses treat you like a class with too many responsibilities, come learn how to code better leadership!