Brown Bag session

Thursday, May 25th, 2006

The unprepared session at agile open prepared us well for the brown bag session Bernard Notarianni hosted subsequently over lunch, to show how they are done in his workplace. These brown bag sessions each deal with a chapter from Quality Software Management (the four volume book series by Gerald Weinberg).

Bernard Notarianni tells what is in the first chapter of QSM

Bernard Notarianni explains the first chapter of Quality Software Management

I’ve participated in many discussions on software quality. Usually, it leads to babble and nothingness… This time was different. Discussion on ‘what is software quality’ was focused, and I learnt a thing or two about it. The format of the meeting is simple. Everyone reads a chapter, there is some discussion on the content, and then the group does one or more exercises – QSM has exercises at the end of each chapter.
They have these meetings every two weeks. At this rate, they’ll be spending the next couple of years working on it. Bernard says it works great for them, and they’ve been doing it for quite a while now – looks like years of fun and learning to look forward to.

The unprepared session

Tuesday, May 23rd, 2006

Raphael Pierquin requested an unprepared session at Agile Open. I guess many people would feel an unprepared session, even without a formal agenda at the beginning would lead to a conversation like this:

unprepared session metaphor

there were two muffins in an oven comic by Adam Hally

People often fear the same of an unconference as a whole. The unprepared session turned out to be exactly the opposite.

The conversation was extremely focused. We used Moo Cow several times during this session. Calling “Moo” helped us to keep laughing, it was a great paradoxical way to maintain focus. Everyone was listening intently, all participants were facilitating the discussion, and we got time to work on some topics in depth. Raphael started off with a difficult question that we delved into, after that we tried a temperature reading because several participants wanted to try it out.

uncommented photo img_9847.jpg

After the temperature reading, we had a discussion on the forces that make it work or not. Because the unprepared session took place in an unconference, participants could (and did) walk in and out of the session at any time. Several people joined in halfway through the temperature reading, after we had done the appreciations. Again it turns out appreciations have a special effect on the meeting. If you join a temperature reading after the appreciations, you miss the atmosphere, and the other participants can not bring you ‘up to speed’, because the atmosphere can not be verbalized.

Neither can the unprepared session. I hope I gave an impression that does it a little justice. I hope to have some more unprepared sessions here at european consultants camp.

Presentation styles

Tuesday, May 9th, 2006

I participated in the presentation zen session at agile open hosted by Pascal van Cauwenberghe. Pascal already did a writeup on the session as a whole.

The main reason for me to attend this session is if I want to be better at creating and giving presentations, I might as well go all the way, look what works for other people and see what fits for me.
Vera, Willem, Kristel and Lieven presenting at agile open This is the group I was in, with (left to right) Vera, myself, Kristel and Lieven.

This session worked very well for me. I took some things away that I applied the next monday, while making a presentation for a client – for those of you who wonder whether going to conferences contributes to the bottom-line, agile open did to mine, and quickly :-) .
I’ve been to several presentation and communication trainings, when done badly, they had the opposite effect – one made me more afraid of giving presentations rather than more relaxed. So hats off to Pascal for making space for a relaxed and fun session. I guess creating and presenting in groups made it a lot more fun and less scary than it would have been experimenting individually.

Practicing in a group was also very productive. in about twenty minutes we created a presentation with three co-presenters, did a trial run with feedback in a few more minutes , and then a re-run for the other participants a few minutes later.

The second run went already noticeably smoother, even though we had no opportunity to update the slides based on the feedback and new ideas we got from the first run.
presentation styles slideWe started with an anti-slide, extra filled with bullets in an illogical order. Vera told a long story somewhate unrelated to the bullets.

To see if the participants read the slide or listened to Vera, we inserted some jokes at the end – if people laughed, they were reading, otherwise they were listening to Vera. Our hypothesis was, that people could either read the slides, or hear Vera speak.

Some participants were laughing, others were not, so we concluded that some were listening, and others were reading. We verified it with questions after the presentation, our assumption seems to have been correct. The next slides were in lessig / takashi style: just one to a few words per slide.

That gives much more…Focus

Slides like this are much easier to read from a distance, and are also friendlier to older people (It’s not called senior management for nothing… ;-) ) .

In our group we discussed about what presentations are used for. In-company presentations are often used as ‘discussion documents’ ‘process documentation’, and more in general, presentations are often also used as handouts (I do that too in courses). It seems presentations are better considered a separate medium from those. Presentations are less cluttered, and handouts, process documentation and discussion documents are better served with more detail than can fit in a slide.

Getting better at presenting takes practice (lots!) and fresh ideas from elsewhere – this session provided both.

Outline the people

Monday, May 8th, 2006

Remembering names and faces after a conference can be difficult. At agile open Raphaël Pierquin suggested we make a group photo, so everyone could add their name to the photo.

To make it easier to find ourselves back in the picture Raphaël used gimp and his daughter’s felt pen to create numbered outlines:

outlines of agile open attendees

Getting this outline was a nice surprise. If you were at agile open, please add your name to the pictures page on the wiki.

agile open photos

Sunday, April 30th, 2006

I managed to get the agile open photos online, a big thank you goes out to Marc Evers , who put my camera to good use. Having someone else take pictures as well freed me up to be more present during sessions. (draw parallells with pair programming).

Some photo’s to give a taste (there are many more photos from agile open than I can fit in a blog):

a large group of participants stand around, as the program is being created on the floor

participants making the program


coding dojo, a pair programming and two other participants looking at the beamer

Coding Dojo (Randori)

a group of people having a break, standing around tables drinking orange juice and coffee

break

five people sit outside on the terrace

break

several people around a table, making a current reality tree

Current reality trees don’t bite

bunch of people having a discussion in a meeting room

round table discussion

dark photo, with Focus slide clearly lit.

Zen presentation

drawing carousel workshop - participants sitting pairwise at a table, in a long row of tables, each pair working on part of a collaborative drawing

drawing carousel

drawing carousel team shows their finished drawing

drawing is released, even though it is not really finished…

agile open program 2006, day 1

thursday’s schedule

Fridays schedule

Friday’s schedule


Tom and Marc discussing, Marc gesturing

Tom and Marc discussing

Bernard and Raphael discussing

Bernard and Raphael discussing

Vera Peeters hosting the xp game

xp game


Barry and several others waiting for the closing session to get started

waiting until the closing session wants to start.

Unconferenced

Saturday, April 29th, 2006

I’m recovering from agile open, still feeling somewhat unconfenced / conferenced out :) . I liked it a lot, biased as always, because I co-organize it… Unlike at some other conferences I visited recently, I was able to attend a couple of sessions I didn’t organize

last and not least, the planned unprepared session, and after that the unscheduled unprepared session, outside on the terrace with wine and excellent conversation.
unprepared session

I believe we succeeded to strike a balance between structure and un-structure, keeping in mind the goal for this conference is openness, and maximum participation from everyone. On the second day we changed several things in the structure based on suggestions made during the opening that day. I had the feeling everyone was feeling more comfortable on the second day, because everyone knew each other a bit better. We may add some get-to-know-your-fellow-participants activity for a next event.

Raphaël suggested we make a group photo, so we can remember who’s who later. Unfortunately, when we got around to it, some people had already left. The mostly broad smiles say more than I could about this event. Wonder full:
participants

Just a few nights of sleep before Agile Open

Thursday, April 20th, 2006

Having Agile Open, is like having a birthday. A big surprise, and i’m not sure what I’m going to get…

It seems we are not slacking off (as I feared in Princess Risk ). We had a standup meeting over skype yesterday, that gave a lot of focus. We have virtual ‘standup’ meetings in a chat window. They last a bit longer than ordinary standups, passing the ‘talking stick’ is more difficult. But they are usually good fun, and quite effective.

One thing we were puzzled about, was wether to do a last-minute marketing effort. With twentyfour participants and seventeen ideas for sessions, it is looking to be a fun-filled conference. Maybe more participants would be even more fun? I don’t know. Today is the last day you can still join though :-)

Ideas for sessions will be welcome until the start of the conference, and possibly on the second day of the conference as well.

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.