Agile 2008 – Before the conference

Arrived in ‘Tronno

On Monday, the Agile 2008 conference kicks off in Toronto.

This is my first visit to Toronto, so I’m using this opportunity to visit some friends and to see the city.

Highlights of the tourist program include a shopping mall, a big pointy building, mock-old buildings, evolution, dinosaurs, the harbourfront, islands and running.

And of course, no agilist can miss the opportunity to visit the big waterfall! 🙂

In between, Portia and I have some work to do to prepare for the “Mirror, Mirror on the Wall… Why Me? Snow White and the Seven Dwarves Kanban” and La technique d’interview des Neuf Cases pour mieux comprendre votre client“.

Hope to see you at one of the many sessions if you are at Agile 2008. More about the sessions later.

Agile usergroups Benelux v2.0

XP usergroups v1.0

Near the end of 2000, some Dutch (and a few Dutch-speaking Belgian) XP enthusiasts got together. They decided to meet regularly to exchange experiences and learn from each other. There wasn’t a lot of material and certainly not a lot of experience, but everybody present believed passionately that we could do a lot better in IT. There was no formal organisation, no legal entity; the meetings were self-organized. Thus was born the Dutch XP Group.

In 2001, the Belgians formed their own group. We discovered that there were other companies in Belgium doing XP and that there were more developers who wanted to do XP. There was no formal organisation, no legal entity; the meetings were self-organized. Thus was born the Belgian XP group.

The two groups continued to exchange information. Meetings were held regularly. Some people went to both user groups. We organised some joint meetings. We were experiencing that XP worked better than anything we had tried before. Not that there weren’t any problems, but feedback from the user group helped solve many problems or answer questions about implementing XP.

Growing up

Following in the footsteps of the London group, we decided to organize a conference. That requires more means and organisation than a user group meeting. So, a few of us set up Agile Systems, a non-profit organisation to research and disseminate knowledge about Agile and Systems Thinking. Thus was born the XP Days Benelux.

The XP Days have grown over the past six years. Meanwhile, the user groups have declined: there were fewer meetings; the gaps between meetings became longer.

Why? Was there no more interest in XP? On the contrary: demand for Agile and XP has grown steadily. All those who talked about XP and wondered how to “sell Agile” were now so busy implementing Agile methods that there was almost no time left to organize meetings.

Agile usergroup v2.0

This year, two new groups were formed: Agile Holland and Agile Belgium. Most of the organizers are new; some are from the ‘old guard’. These groups have taken a fresh start: meetings are being organized again, attracting new people to the group. The focus has widened from XP, the first agile love of many of the original group members, to the more generic topic of Agile.

Many of the participants of the new meetings have never heard of the original XP groups. The main subject is no longer “why XP?” or “how do I sell XP?” The main questions these days are “how do I implement Agile effectively?” and “how can I scale Agile enablement?” because there’s more demand than supply for Agile.

I’m glad there’s still an interest and a need for a local user group for local people. We can learn from the past: a self-organizing group like this can only remain alive and fresh if its members really get involved.

This concludes today’s history lesson.

Now it’s your turn. Contact the groups via the Belgian group mailing list or the Dutch group mailing list.

Business Value Game

Where does ‘Business Value’ come from?

In the XP Game you get Story cards with a Business Value number. In the game, teams compete to release as much ‘Business Value’ as possible by implementing the game’s stories. Planning is very easy: developers estimate the cost of each story in points; the customer orders the stories per Business Value/Cost.

If only it were that easy in real life.

How many of you have Stories with a Business Value on them? The projects I’m currently working on don’t have a Business Value estimate (yet). How are stories prioritised? By ‘gut feeling’, by risk, by deadlines… It’s not always clear. How are projects and releases prioritised?

Come and play the Business Value Game

To explore those questions, Vera and I have designed the ‘Business Value Game’. Like the XP Game, it’s a friendly competition. This time the players are salespeople who have to deliver features to customers to earn as much money as possible for the company. They have to keep their customers happy or risk losing customers.

The game is shorter and uses fewer props than the XP Game. No balloons, just a bunch of cards that represent customers, customer requests and stories. Like the XP Game, the Business Value Game will be made freely available for download, using a Creative Commons license.

The first tryout of the game will be held on August 13th at Cap Gemini Belgium in Diegem. See the Belgium XP wiki for more information and registration for this free event.

See you there.

Agile 2008

Agile 2008 is coming near

I’m glad I’m going to Agile 2008 in Toronto this year.

I’m glad Portia and I will present two sessions.

Mirror Mirror

Mirror, Mirror on the Wall… Why Me? Snow White and the Seven Dwarves Kanban” is a mini-adventure of self-discovery to improve personal effectiveness. Think “Kaizen meets Agile Fairytales.”

Huh? What do a bunch of dwarves and an Evil Queen have to do with Agile? In this session you learn more about yourself, how you see others and how you can improve working with others. You learn to recognize the strengths of each (potential) team member. With the help of fairytale characters, you can create and maintain teams that play to the strengths of their members.

Why is this important? Software development is a team sport. I’ve been on some great teams. I’ve seen aligned teams in sports, theater and IT outperform non-aligned teams by a large margin. These two ingredients, efficient communication and playing to the strengths of members, were vital in each case.

Nine Boxes

La technique d’interview des Neuf Cases pour mieux comprendre votre client” is a game where participants learn to perform structured interviews. The interview technique comes from the Solution Selling sales process. The Nine Boxes allows you to discover

  • The real root causes of the problems your customer experiences
  • Who is affected by the problem and how they are affected
  • Co-create a vision of the future where the problem is solved

Huh? What does selling have to do with Agile? If we want to lead meaningful lives, we must attack the root causes of our customers’ problems. We must really understand the system. We must make all stakeholders enthusiastic about solving the problem, so that they will help bring about fundamental changes. We must give them back hope.

And then we can start writing user stories… IF AND ONLY IF software will help us to deal with the customer’s bottleneck.

See you there

I’m afraid to get lost in such a big conference, with so many sessions and so many people.

I’m glad I’ll be seeing friends inside and outside the agile world in Toronto.

Agile 2008, 4-8 August 2008 in Toronto

Why bother with bottlenecks?

Why?

Bottleneck Game at XP Days London 2005

Portia writes about a participant of our Bottleneck session asking her about the relevance of a session on (industrial or manufacturing) process improvement techniques at an IT conference. Portia already told me she had the same reaction when she attended this session at XP Days London in 2005. If you look carefully, you can see Portia at the right, a bit bored as she’s waiting for the bottleneck.

Moreover, with terms like ‘exploit’ and ‘subordinate’, the 5 focusing steps don’t sound very friendly. Is this just another management fad ‘to squeeze the workers’? Can we apply manufacturing ideas to IT? Isn’t the manufacturing metaphor (or the house building metaphor) responsible for some of the worst ideas in IT?

That participant took the first step in understanding: they asked “Why?”

What is it about?

The session (and the Theory of Constraints) is about creating meaning and value by really understanding systems.

To do this, you need to:

  • Design systems that fulfill a meaningful goal.
  • Take a step-by-step approach to diagnose problems.
  • Find real cures by going beyond your area of responsibility, beyond your comfort zone and considering the system as a whole.
  • Involve everybody, to continuously challenge assumptions and long-standing traditions to create lasting improvements.

These are things I use every day in my life and my work. Are these things you could use in your work, in your life, every day?


Thank you to Portia for excellent writing advice and helping to edit this entry.