The Business Value Game: v1.1 released

Business Value Game v1.1

Thanks to the feedback and ideas playing v1.0, Vera and I have released an update of the Business Value Game.

What’s changed?

  • The session description contains more examples and explanation to fill in the iteration score sheet.
  • Some corrections to the text in the manual.
  • Client cards can be folded to stand up for extra clarity.
  • Rebalanced the process improvement cards to make process improvement more attractive.
  • Story cards are numbered to make it easier to see if all cards are available.
  • Pictures of the game being played, by Portia Tung.

There are no major changes, this is mostly fine-tuning of gameplay. We have lots of ideas for challenging prioritisation cases. To incorporate all those ideas we’ll have to make a 9 iteration version of the game.

Go out and play!

Do you want to learn about “Business Value”, prioritising your backlog, portfolio management and all the challenges that salespeople and account managers face daily? Do you want to experience the benefits of working with short iterations and releasing early? Do you want have fun while you learn? Download the Business Value Game, print the cards and organise your own game.

Creative Commons License The Business Value Game by Vera Peeters and Pascal Van Cauwenberghe is licensed under a Creative Commons Attribution-Share Alike 2.0 Belgium License.

Business Value Game v1.1 on tour

Agile Holland Conference

The Agile Holland group organizes their first one day conference on October 24th in Amsterdam.

Vera and I will present the Business Value Game v1.1, which incorporates the feedback we got from participants at tryouts at Agile 2008, the XP user group meeting, Brain Train and Agile Business Conference.

Scandinavian Agile Conference

Agile Finland organizes the Scandinavian Agile Conference on October 29th in Helsinki.

I will present the Business Value Game with some Finnish coaches at the conference.

XP Days Benelux

The XP Days Benelux conference on November 20th and 21st in Eindhoven also features the Business Value Game, this time presented with Vera and Portia.

<Your company>, <Your usergroup>

Do you want to learn about “Business Value”, prioritising your backlog, portfolio management and all the challenges that salespeople and account managers face daily? Do you want to experience the benefits of working with short iterations and releasing early? Do you want have fun while you learn? Download the Business Value Game, print the cards and organise your own game.

Creative Commons License The Business Value Game by Vera Peeters and Pascal Van Cauwenberghe is licensed under a Creative Commons Attribution-Share Alike 2.0 Belgium License.

Where do they come from?

Where do participants to XP Days Benelux come from?

Places are filling up nicely for the upcoming XP Days Benelux on 20-21 November. It looks like we’ll have another sold out conference.

The XP Days started as a local conference, to enable participants to get a taste of Agile without having to travel too far. We always attracted a good mix of local and foreign presenters. Local presenters bring stories that are recognisable to the audience. Foreign presenters bring in new ideas and techniques.

As you can see from the table, three quarters of the presenters are Belgian or Dutch. The other presenters come from 7 countries.

Belgium 24
The Netherlands 19
France 6
Finland 3
Great Britain 2
United States 1
Germany 1
Italy 1
Switzerland 1

The geographical distribution of participants is even more marked: 85% of all participants come from Belgium (45%) or The Netherlands (40%). The other participants come from the seven countries mentioned before, plus Sweden.

But where are the Luxemburgers?

Show me the money

Playing with business value

This week, Portia and I hosted two runs in London of the “Business Value Game” that Vera and I developed. As usual, we had a lot of fun hosting the session and got good feedback from the participants.

Brain Train

Portia started the Brain Train sessions as a way for friends and colleagues to get together to experiment with new sessions and games. Earlier this year, we presented the “Real Options Space Game” at a Brain Train session in the Royal Festival Hall.

Last Monday we were back in the friendly lobby of Royal Festival Hall. As players started trickling in we grabbed a few tables and chairs to set up the game. Portia and I each coached one team through the six iterations of the game.

Each team used different strategies. For example, one team lost an unhappy customer because they concentrated on the other more lucrative customers, while the other team ensured that each customer stayed happy. In the end, Portia’s team won, even though they lost a customer.

After the game, we held a retrospective to see the good, the bad and the puzzling. The participants learned (or confirmed) some lessons about customer interaction, iteration planning, release planning, communication and teamwork. We’ll publish the results of the retrospective.

Thank you Eamon, Roshni, Jenni, Mark, Ioana, Al, Mohan, Daniel, Dot, Tamas, Eben, Ashutosh, Archie and Maria for playing and giving feedback.

Agile Business Conference day 1

The next day, I attended the first day of the Agile Business Conference. The highlight of the program was a funny and energetic keynote talk by Rob Thomsett on Agile Project Management.

One of his learnings is that when we borrowed engineering and construction project management models we also inherited their prevailing culture. The relationship between “IT experts” and “Users” (a denigrating term) has always been adversarial.

Agile Project Management is about true collaboration and is based on a set of values:

  • Open: full participation and ownership by stakeholders.
  • Trust: team members and stakeholders are professionals who can be trusted to be committed to the project and the organisation.
  • Honesty: all people impacted or involved have a right to be told the truth; asking for help is a sign of strength.
  • Courage: Undertaking projects requires courage in many areas like telling the truth and asking for help.
  • Money: projects consume money. This requires a fiscal and ethical responsibility to be shared by all team members and stakeholders.

Rob concluded with some of concerns (silver bullet syndrome, lack of whole-of-life view, focus only on technical issues, lack of cultural awareness) and drivers (faster delivery, change friendly, more enjoyable, real teams, great values) of further Agile distribution.

In between sessions I talked to some acquaintances and met some new people. Together with Exoftware (thanks Andy!), we invited people to come to the next day’s Business Value Game. By then, we had already updated the game with the feedback from the Brain Train tryout.

Agile Business Conference day 2

After the opening keynote we played another Business Value Game with 13 participants. This time my team won! Again, the players had fun and learned lessons about planning, teamwork and prioritisation. It’s interesting to see how players react to the time pressure of the game:

  • one of the teams used some extra time to come up with elaborate strategies and tried to make decisions before they had all the information.
  • one team discarded information because they felt they didn’t have enough time to examine the information.

All teams could have done better and worked faster if they had shared more information in the team and if they had only taken decisions when they needed to. But that’s the subject of another game, the “Real Options Space Game“.

Agile Business Conference – closing

One of the highlights was seeing Ole and Jenni from GoAgile in Denmark again. Thank you for the gift and the great conversations about sessions, presentation techniques and Agile project management. We still owe you an explanation of Real Options. Most of all, thank you for your enthusiasm.

The conference closed with a presentation on the “Responsibility Model” by Christopher Avery. Chris explained the difference between being given accountability and taking responsibility. His model explains how we typically react in the face of problems. Portia has a good writeup of the material. On the way back Portia and I had a lot of fun going through each of the steps in the model in an exaggerated way, because one of the “Keys to Responsibility” is Awareness of how we (re)act.

Come and play!

We got good feedback on the game. Portia, Vera and I are busy working on v2.0 of the Business Value Game.

If you want to play our games, come and see us at the following fine events:

29/10/2008 – Scandinavian Agile Conference – Helsinki – The Business Value Game

20-21/11/2008 – XP Days Benelux – Eindhoven – The Business Value Game and Mirror, Mirror on the Wall

11-12/12/2008 – XP Days London – London – The Real Options Space Game and a new game by Vera. Exciting!

Or you can download our games and play them at home.

Watch this space for the release announcement or come and play with us at one of the upcoming conferences and seminars.

Velocity is measured, not estimated

Finally! We have a velocity!

One of the teams I coach is getting close to their first release using Agile methods. Our first planning and estimation effort was difficult because we had no previous stories to compare with and no kown velocity. So we had to estimate what our velocity would be. Not a very comfortable position, but what can you do if you have no historical information?

It turns out that our estimate was not too far off. We didn’t give a “point estimate”, one date. We gave a range of dates between a “best case” and a “worst case” scenario. The size of the range between the two dates indicates our uncertainty about the estimates. We’ll probably deliver a few days before the “worst case” date, which is an acceptable date for our customer. Our releases are not timeboxed, they are scope-driven.

The next release should be easier to plan and schedule now we have a velocity and a set of implemented stories.

Defining the next release

The next release isn’t very large. In about an hour we wrote the stories and estimated them. We reused many of the existing stories. We estimated the stories in story points by comparing them with the existing stories. This release will be about one third the size of the previous one.

We know our velocity, therefore we know how many mandays we need. We know how many men and women are available for the project and when they’ll be available, therefore we know when we’ll be done in the best and worst case.

Easy.

This one will go faster!

When we calculated the number of mandays, the developers exclaimed that this number was too high. They argued that their velocity would be higher on this release because they wouldn’t have all the startup costs of the first release. They were now more experienced.

To which I replied: We’ll see…

Maybe we’ll have lower startup costs. Maybe we’ll work faster because we have more experience. If we do, our burndown will tell us soon enough. It would be nice to end up closer to the “best case” than the “worst case” estimate this time. In any case, we need some time to clear out some ‘technical debt’. We’ve decided to invest 10% of our time in debt-reducing work.

IF we deliver sooner than expected we’ll take on the next release sooner than planned. There’s more than enough work waiting to be done.

And next time we’ll schedule using our improved velocity.