Agreeing on Business Value slides
Here are the slides for the “Agreeing on Business Value” session we ran at Mini XP Days Benelux 2011 and will run again at the SPA conference in June.
The exercise uses a case study that’s not published, so you can’t peek and prepare for the session 🙂
“Agreeing on Business Value”
Portia Tung and I ran the “Agreeing on Business Value” session at the Mini XP Days Benelux 2011 conference. In the workshop participants have to create a “Business Value Model” for a case we provided. The Business Value Model shows the most important goals and measures of the company and the relationships between goals. We often run this workshop to let a team come up with a common definition of “Business Value”. As a result of the workshop, everybody’s has a clear and common understanding of the value the project or product is going to deliver.
We asked the teams to add what they learned at the workshop on the posters. Here’s a gallery of the outputs of different groups. Click on the images to get a larger picture.
In the model different types of goals have different colors: financial goals are blue, organisation goals are green and people goals are yellow. At the top are the “lagging measures” (those that can only be measure late). At the bottom are the “leading measures” (that can be measured early) that will be used to predict the achievement of the desired lagging goals. Arrows indicate that one goal has an effect on another. You’ll see that most things are interrelated. The good news is that achieving one goal can help achieve other goals in reinforcing loops. The bad news is that you may have to achieve many subgoals to achieve your desired goals.
This team identified the following learnings:
- Makes a complex project more clear
- Business alignment. Today business cases are made individually
- Helps to give an overview of goals for all stakeholders
- Make decisions at goal level, not at feature level
- (You can use this for) portfolio management!
- Thinking about measures
Here we se a simpler model, but still representing the financial, organisational and people goals with their relationships. Everything leads to “Make Profit” 🙂
What they learned:
- When we talk about business value, we need to think about how to measure leading and lagging indicators
- Adding the relationships generated new insights
- Eliminate “business value” that doesn’t really add value
Another very clear model with positive (+) and negative (-) effects between different goals. In the end, it all results in “Cost Cutting” 🙂
What they learned:
- It starts with a vision
- You involve everybody
- To build a model, iterate over the following steps until satisfied:
- Identify goals
- Define Lagging and Leading measurements
- Identify relationships (“Diagram of Effects”)
This model has exactly one leading and one lagging indicator per area. Together, the goals result in profit.
This team created a diagram of what they learned:
- Value is not just money
- Value must be measurable
- We have leading (“early”) and lagging (“late”) measures
- We need to identify the relationships between the measures
This team considered more lagging (yellow) and leading (pink) goals. Many of the goals have more than one possible measurement. If you have multiple ways to measure a goal you can choose the cheapest measure to collect or find some data that’s already being collected.
The important points for this team:
What the presenters learned
- Everybody got the same case, but there are differences in the models. There is no “right model”, the team has to find one that’s useful. Over the lifetime of a product or project the business value model will probably change, as different goals change in importance
- The case is not too simple, and there’s lots of information, just like a real project. Despite that complexity teams of six “strangers” came to a clear agreement on the goals of a project within 90 minutes. How long does it take in your project to come to agreement on goals and priorities. If your projects are like mine, probably the whole duration of the project 🙂
- Making our definition of business value clear, finding ways to measure and thinking about effects and relationships helps to come up with new insights
- Participants don’t ask many questions. We were available the whole time to answer questions about the technique or the case, but despite having real live “customers” in the room, participants concentrated on the written materials
- We started by describing and drawing the company vision on the whiteboard. Most teams quickly lost sight of the vision. Once they “rediscovered” the vision, they found that it answered some questions about value and priority. It would be good to remind people of the vision before every turn. Maybe we could do this in our work too? Why not start each project meeting with a reminder of the vision?
If you want to know more, head on over to the agilecoach.net site where you’ll find more about Business Value Modeling and some other useful tools.
If you applied any of these techniques, let us know how it went.
Portia Tung and I will present “Agreeing on Business Value” at the SPA 2011 conference in London, June 12th to 15th.
In this interactive tutorial you’ll be able to apply “Business Value Modelling” on a case study, to decide on the goals and definition of value for an improvement project.
Come and play with us!
Alexander Nowak of the Microsoft Community of Practice of Cap Gemini Belgium has written a description of the tryout of the “Agreeing on Business Value with Systems Thinking” that will be re-run on April 1st at Mini XP Day Benelux.
In his post he describes the following main points:
- Business Value is multi-dimensional and not always easy to express. The key lies in the measurability of things.
- The “Business Value Model” is a technique to set the context of the “big” why and communicate this across the organization (small or big).
- It is built around the concepts we are mostly familiar with (and borrowed from other techniques).
- The “Systems Thinking” part comes into play to discover relationships between goals, capabilities, stakeholders and measurements and risks. When you turn a knob here, something will happen on the other end… and vice versa.
- A business value model is not carved in stone. You must always evaluate if what is described (or better drawn) in the model actually reflects reality.
- This visualization is important for communication. Doing the value exercise can be an eye-opener for the people in the project and/or organization.
- The “Business Value Model” should be the origin for all user stories.
Yes. That’s it. Couldn’t have said it better myself 🙂
You can see the outputs of the workshop in a previous blog entry. Read more about it on the AgileCoach site.
Hope to see you at the conference!
Portia Tung and I co-present “Agreeing on Business Value with Systems Thinking” at this year’s Mini XP Day Benelux. This is one of the twelve sessions from XP Days Benelux 2010 that have been selected to re-run.
See you on April 1st in Mechelen.