Princess Risk

Friday, April 14th, 2006

As Agile Open is drawing near, pascal writes about how we manage risk. We use a simple brainstorming process, filling the risk table from left to right (event/what , probability, impact, mitigation). This has proven very effective. I believe it also helps us to relax, and share our concerns. The biggest concern for me right now is meta – after organizing a couple of conferences (three xp days and now the second agile open), we risk becoming unfocused.

Pascal mentioned the princess risk – the risk that a princess arrives at the conference. To him it signifies risks we did not anticipate in the past. These things will happen. For me, the princess risk entry in the risk table now also signifies as a call for myself to stay vigilant. The probability is stated as 50%. After three xp days benelux and one agile open, we should really have updated it to 25%, as a princess arrived at only one of those four events… (we introduced the risk after the second xp days benelux, at which a Belgian princess showed up, and threw us into chaos).

Unanticipated risks happen. Preparing scenarios prepares us mentally – we are aware that there are things that will not go as planned. Last year there was also at least one good thing that happened unexpectedly for me. Agile Open helped someone change his life.

It changed mine too. Co-facilitating an experiential workshop on congruent communication made a deep impression on me. I couldn’t really believe I was doing that, and yet I was doing it :) . We’ve continued to develop this workshop as we are making the tools we use our own. We’ve ran it in various configurations, most recently at SPA and xp days france. We’ll be running it again at agile2006, where it has been accepted as a tutorial (“Balancing act – simple tools for feedback, communication and courage” – I would include a link, but the programme seems to be online as a PDF only).

I’m glad. Risk is only a Princess – Value is King (or Queen :-) ) at agile open.

Continuous Integration and Testing (un)Conference

Tuesday, February 21st, 2006

Continuous Integration and Testing Conference April 7-8, 2006 – Chicago, IL, USA. I won’t be able to attend, but this open space event might be worth your while. I don’t know the organisers, but they seem to know themselves pretty well ;-) :

Jeffrey and Paul have been planning the conference for more than 9 months and feel that just doing it is better than languishing in analysis paralysis. Early April was targetted as a good time.”

I hope next year Jeffrey and Paul will call it an unconference. At the agile open last year we had some participants who had missed the fact there was no conference program. On the other hand, most of the CITCON site is about open space and the open space rules
Through Lasse’s weblog – CITCON in Chicago

» Around the MashupCamp fire

Tuesday, February 21st, 2006

» Around the MashupCamp fire | Between the Lines | ZDNet.com

Hadn’t heard about this before, it’s happening now apparently. Mashup camp. Made me think of mashups (two music tracks combined, a fast and easy way to create remixes these days). Apparently it is about combining API’s (of the web 2.0 kind) in various ways.

It’s always nice to see the now familiar open space rules posted on a flipover, and seeing the photo of Ward Cunningham, I’m curious if he’s going to come up with something as simple and fascinating as the Wiki again. The session title “Tools for Ah-has: Things that help you make and share ideas” sounds tempting…

photo by Cirne