I particularly liked the draft on Financial Options, it explains a number of not so intuitive financial instruments and techniques (e.g. naked short selling and futures) in such a way that I find them easy to understand, and possibly explain them to others. Not a bad thing to have in turbulent financial times. Chris’s goal is to make them  understandable by ‘basically everybody’ - I encourage you to go and read it, and give him some feedback on bits you don’t understand.

Emmanuel Gaillot just blogged about our upcoming French Refactoring Training.

January 28 and 29 at the office of Octo Technology in Paris. This training will be in French. We ran it together in-house (also in Paris) and it worked quite well . The training was good fun, we did even more things dojo-style (including demos) than I normally would, and we made time for hands-on systems thinking. I think with the experiments we’ve done this year, that we’ve finally found a good way to do systems thinking with programmers. It seems to be a bit more intuitive for managers and coaches,  but presented in the right way, it turns out developers find it eXtremely valuable. Surprisingly (not ) the topic the developers chose for their diagram was not entirely technical: how too much labour turnover was hindering their productivity and maintenance.

In other other news: the QWAN newsletter is out. It has some instruction on how to do your own Temperature Reading, conference reports and the public courses agenda. Enjoy!

Now it is time to relax after a  busy and period. Maybe I’ll finally get around to posting photos from all the conferences we’ve been to since october…

Marc suggested to do part of the upcoming newsletter as a Temperature Reading, so besides getting some information, our readers also learn a technique, and it helps us structuring our own reflection over the past year. It’s been about a year since Marc, Rob and yours truly sat together after xp days london to discuss closer collaboration with courses and coaching (but still as loosely coupled as possible, because we like our independence).

A Temperature Reading has five questions, the order of which you can vary, depending on the context (see Temperature Reading for explanation and the default order, I’m going to do something different here).

1 New Information

We proudly presented QWAN = Quality Without A Name

We started handing out these rubber ducks at CITCON Amsterdam, for those cases when we are not around to pair (program, brainstorm, reflect, be innovative) with. Talking out loud helps, and ‘rubber ducking’ is a well known technique for this (e.g. Kathy Sierra writes that talking to pets works even better. We came across it the first time in the Pragmatic Programmer ). We chose QWAN as a name, because we are still inspired by Christopher Alexander’s early work on patterns (Timeless Way Of Building) most notably. QWAN is a label for stuff done by Rob Westgeest, Marc Evers and yours truly, often in co-operation with others.

QWAN co-created a bunch of new courses and workshops in 2008: eXperience Refactoring (also with Octos’ Emmanuel Gaillot), Unit Testing Masterclass, responsibility driven design with mock objects, dirty jobs (with Tjakko Kleinhuis), pimp my retrospective (with Topic’s Nicole Belilos), political games (with Emmanuel Gaillot), story testing with Rspec, and a revamped rightsizing your unit tests (and then some that I forgot. This collaboration seems productive, many more than last year it seems. We supported conferences in one form or another, e.g. by sponsoring, as co-organizers or ‘just’ running a session: CITCON Amsterdam, several Agile Opens, XP Days Benelux and London, ESSAP summerschool, Agile2009, AgileHolland.

2 Appreciations

We’d like to thank everyone who participated in our courses, conferences and workshops. Your enthusiasm and feedback helps us to improve and, not least, have fun in our jobs. Everybody who provided encouraging feedback when we published our brochure earlier this year. Especially Nynke Fokma, Becky Winant and other keys for giving detailed suggestions for improvement. We’ve had several great customers (you know who you are), who created amazing conditions for us to focus on our work. Thank you!

3 Complaints with recommendations

We’ve made some progress in supporting ourselves with a Customer Relationship Management system. There are still some improvements that would make our work easier (usability) and that of our customers (sign-up and notification of new courses). (Marc wishes for a more sustainable pace. I’m careful what I wish for - a more sustainable pace would be nice, but I’m also quite happy with our productivity, passion and income at the moment)

4 Puzzles

We made progress in selling open enrollment courses, and are still puzzling on better ways of selling those (as well as making it easier on our customers to plan and buy participation). The context for courses seems to be shifting at the moment - working more effectively has value, but many large corporations have the knee-jerk reaction of putting all training on hold when sales slow. At these corporations people have little time for training when things are good - too busy, and no budget for training when things are bad. Luckily we also have customers with a long term perspective, who invest in training, education and hiring continuously.

5 Hopes and wishes

We hope the ‘interesting’ economy will mark the breakthrough of lean and agile ways of working in more places. We hope to carry out more integrated on-site coaching … With integrated we mean doing whatever works best in a given context : a whole systems approach using combinations of lean, scrum, extreme programming with ’soft’ skills inspired by Satir and systems thinking.

We wish you a healthy, fun and prosperous 2009, and look forward to collaborating with many of you.

(meta-appreciation: thanks to Marc for coming up with the idea for a Temperature Reading, and giving feedback while listening to the items while writing them. Thanks to Marc & Maroesja’s kids Maris, Marden and Marijn for providing the necessary distractions )

The 2008 conference was quite good for such a large event. Things that contributed to it were, in my opinion, scrapping experience reports as a separate track and instead having lots of experience reports everywhere as well as the breaking acts and questioning agile stages. Yes, you can have those topics spread out, but having those topics front and center (what is the first thing you see when you look at the conference? its the stages. So the first thing you see is: ah, critical thinking, wild new cideas).

If you want to support new ideas, and at the very least keep up the outward appearance that the agile community invites and supports them, leave a comment on David Andersons’ blog post “The case for an agile fringe” .

I also left one at Johanna Rothmann’s (2009 conference chair) response “I’m Disappointing Already” outlining some of the forces I’m seeing. Johanna ems to take it personal, which I think is unfortunate. Sometimes folks in the kanban camp seem to do the same - getting their sessions rejected for earlier conferences must have been very painful. The reasons for rejection were probably systemic, and it seems some of the systemic reasons have been fixed in 2008, now 2009 seems to be sliding back (and yes, kanban is now establishment, but it will happen again to new new stuff).

So, let’s stop taking it personal, and improve the system; no regression, if we can easily prevent that please - carry out one refactoring “replace experience reports stage with fringe stage”, that’s it.

That’s it for today, maybe I’ll post more later. I’m going back to xp days london (which is one big fringe lots of new ideas and critical thinking going on, and the open space is an integral part of the program, which seems to work fairly well at this scale.).

What is a dojo?

The dojo takes its’ inspiration from martial arts, where practitioners get together to repeatedly practice excercises (’katas’), amongst each other or guided by a teacher.

Coders dojos exist in many shapes. The form I often use is called ‘rand

ori’ : one or two people prepare an excercise, explain the excercise to the group and start pair programming on the excercise in front of the group, using a video projector. After five or ten minutes one of the original pair rotates out, and someone from the audience rotates in. Rotation continues every 5 or 10 minutes.

yours truly and Eric Lefevre kicking off the Randori

Benefits

• Improve your skills by doing, and seeing other people do it (also teaches small things about editor etc.)
• challenge and be challenged: accept criticism, defend your ideas, deliver criticism in such a way that others are encouraged to act on it
• Learn how to better work in really, really small steps. If you want to rotate out in 10 minutes with a green bar - all tests pass - you have to

@ CITCON Amsterdam

This is also the form Eric and I used at CITCON Amsterdam a few weeks ago. We both had posted a coders dojo on the open space schedule. I wanted to do a dojo with Mockito (a relatively new mock objects framework for java), so that I could try out a modified excercise for an upcoming training on Responsability Driven Design with Mocking. Eric wanted to do a kata on legacy code, so that he could experiment with an excercise he uses in courses.

We decided to apply some courage and try to see if we could combine the two: use Mockito to add tests to Eric’s case. We started after very little preparation: while we were preparing a heated debate with other conference attendees on how to teach mocking and what (not) to use) already started… We introduced the case and started to work towards adding a test. We found a defect in the only test present (it was not completely legacy code ), and we let the audience decide whether we should fix the test first.
The audience decided we should fix the test. We listened. Therefore we did not show how to use Mockito… Fixing the test eventually took the better part of the coders dojo, and we never got around to having the participants to try out Mockito to make a test running. Eric already summarized what came out of the mini retrospective at the end of the session.

The audience vs. Ivan Moore and …

Coding in front of an audience can be confusing at times

A test is not worth fixing, if it is the only one you have.

I would normally delete this test, guess its intention(s) and re-write the test from scratch. The reason this test was so difficult to get working, was that it was trying to do multiple things. In making the test work, it started to test even more things, so while fixing it, it became increasingly more difficult… If we had rewritten the test, we would have discovered this early on. We then would have noted the other things to test down on our ‘to do’ list, gotten a green bar quickly and then moved to the next item on our to do list.

Programming as a spectator sport. Henk Van Voorthuizen, Marc Evers watch Intently, Jamie Dobson takes notes (he was making a diagram of sorts I believe).

Some things I learned

Having some of the most clever bastards of Europe in the room made this session extremely interesting. It definetely showed me there is ‘more than one way to do it’, and that includes refactoring and adding tests to legacy code. Some will do nothing without a test, some will use automated refactorings only (me) and then add the first test ASAP. Many of these strategies work most of the time… “Many people can be right most of the time, not all people can be right all of the time”, and that shows in a dojo. Most strategies would work to make the situation of the legacy code base better (better factored and/or more tests), but changing strategies every few minutes does not ;).

As Eric says, I’m sure we’ll do better next year. One thing I would try would be to spend more time at the start demonstrating and setting out a direction before rotating in someone from the audience. That way, I would expect less confusion by the participants, and more work in the same direction. This is what I normally do during courses, but the session slot had so little time that we (erroneously) skimped on it.

In the meantime, I’ll be doing some more experiments in (ab?)using mocking tools to shorten the “time to first test.”

Credits

• Laurent Bossavit and Emmanual Gaillot for popularizing the idea of a coding dojo
• The writers of DeliberatePractice for explaining some of the benefits of a dojo
• Marc Evers for making photos (and lending me his camera during the dojo)
• Eric Lefevre for the first writeup
• The participants for making this a very interesting dojo

Title slide, with a photo by Colin a pimped ‘Lemon’ at the ‘24 hours of Lemons’

Slots there are just 45 minutes, so we made an interactive presentation with two short excercises: we’re going to ask participants suggestions on how to ‘wreck’ a retrospective and then spend more time on how to ‘pimp’ one, followed by our own favourite pimpin’ practices. We made all the slides like the one above, some pimped cars, some wrecked, and some plain strange (as well as Saint Nicolas on his horse). I notice with slides like these, I’m much more looking forward to giving a presentation.

Curious? Join us at the AgileHolland conference Oktober 24 in Amsterdam or read on for the full session description.

Do you have a retrospective regularly? Are they always effective, and always yield useful actions? Does each and every member of your team look forward to it? Does everybody participate actively?

Keep it that way! Your retrospectives are like a flashy new sports car…

Or do your retrospectives turn boring after a while? Do the participants yawn loudly? No new and refreshing results? Does this result in reflection happening less and less often?

Then there is only one solution: pimping!

In this session we’ll take the participants to our garage, and figure out how to transmogrify an old, steady retrospective into a super hot Retro. We’ll share our experiences and tips, and would love to hear yours. So, whether your Retro is a dented old Lemon or a shiny Ferrari, there’s always something to take away from this session.

Credits:

English session description based on dutch description by Nicole

photo by Colin has a Creative Commons Non-Commercial Share-Alike license

]]> http://me.andering.com/2008/10/20/pimp-my-retrospective/feed/ http://me.andering.com/2008/09/15/where-is-willem/ http://me.andering.com/2008/09/15/where-is-willem/#comments Mon, 15 Sep 2008 07:04:28 +0000 Willem van den Ende http://me.andering.com/?p=322 Sometimes people around me wonder where I am. Maybe you have too. I used to say, I don’t travel much, but I realized that is because some of my colleagues travel even more… So I added a list of upcoming trips to the sidebar of my blog. You can also subscribe to my trips through dopplr. I hope this makes it a little easier to meet up with other people while I am travelling.

The travel feed does not describe that clearly what I’m up to (only if you click through a couple of times), so I guess I’ll still be posting here about upcoming events every once in a while:

• Paris, next week, will see me and Emmanuel Gaillot co-present an in-house eXperience Refactoring in French - “des excursions dans le Rémaniement continu”. I have been brushing up on my french, and we have been talking French during the preparation. I am looking forward to it. We have been making a number of improvements to the course, e.g. a new exercise and the slides look intriguing in French
• Helsinki, 29 October sees me and Marc Evers co-present the revamped “right-sizing your unit tests” workshop at the Scandinavian Agile Conference. The past years we toured conferences mostly with systems thinking and other people oriented sessions (e.g. cultural patterns), we thought it would be fun to give people a taste of our technical sessions as well.
• Eindhoven, 20 and 21 November - together with Bath, UK one of my home towns -, sees yours truly and Rob Westgeest with a demonstration of story testing with rspec at XP Days Benelux and Responsibility-driven Design with Mocking with Marc Evers and Rob.
• London, 11th & 12th December, I look forward to join Rachel Davies in co-facilitating the large open space at XP day London. It is already their eighth conference, and the XP day London organisers show courage by going with a completely different format - less presentations and more interaction between the participants through Open Space. I think it is fitting. As agile software development progresses, practitioners need a place to push boundaries and work on problems they are (still) getting to grips with. With the high caliber audience that xp day usually draws, this should make for interesting topics and lively discussions.

That’s it for now. I will probably go to London and Bath somewhere in October as well. I don’t know when yet.

Marc, Rob and I have been busy for a while, thinking about repositioning what is soon to be formerly known as eXperience Agile. We were feeling that what we are offering is more than ‘just agile’. We also want to reach pragmatists on the other side of the chasm, who don’t respond well to the zeal that seems to rear its’ ugly head around methods every once in a while.

In short, We’d like a new website, so that our regular customers can easily find out which courses are forthcoming. We want new versions of the brochure, so that people can see the new courses, and we want to send out mailings more often, so that we can keep our clients and alumni informed on interesting conferences and new developments. There must be a system to all this, most likely similar to a tale of website traffic. And we’d like a new name and logo, so the brand fits better with our aspirations and activities.

Not that we know much about branding (or are necessarily fond of it - I’ve even said Branding is for cows in the past). But we got to do something

So we spent a day brainstorming new names, and finally found one that we all liked and had an available domain name that was not too long. If I remember correctly, Rob came up with the name and it fits well with the name of Marc’s company (Piecemeal Growth) and mine (Living Software), as it is also inspired by patterns.

Rob and Marc brainstorming on the new name

We also decided to do some experiments. We moved slowly, we were all available at different times and registering the domain name took longer than expected.

One of the experiments we decided to do is sponsoring a conference with money - usually we sponsor conferences with blood, sweat, and tears (and a good portion of laughter of course). And then it took us a couple of months to get moving on it.

We were procrastinating, because not ‘everything was ready’…Sounds like a software development project, doesn’t it ;). We did not have a logo, nor did we have the new website we wanted so badly - the current one is inconvenient to maintain and could look nicer.

This week, I decided to get moving, even though the sponsoring deadline of the conference had already passed. Luckily, one of the organizers mailed me if we were still interested in sponsoring - I had talked to him at the agile2008 conference already. That was excellent timing.

So I decided to go for it, and pay for the sponsoring. Doing that helped us to move forward. The conference organizers helped us by giving us a deadline - the logo had to be in by friday to make the printed programme

We felt we can always iterate over the logo and change it later. We also had to give them a url to the website. Oops. Ok, so we don’t have the flashy new site yet, but we have the domain name, so we point it to the old one for now. Ah. brochures. We should have something to hand out at the conference. Hm. The previous one was quite succesful, but we didn’t get around to making a new one. What changes do we really, really want to make so we can send it to the printer this week? Let’s take out the course schedule so the brochure lasts a bit longer, add a new course and announce the rebranding in the brochure.

By now, I hope you are curious about which conference we are going to sponsor, what our new name is going to be, and what our new offerings are. Be the first to know, and subscribe to our - soon to be revamped - newsletter - leave your e-mail address in the box at www.experienceagile.eu or contact me directly.

Credits: Thanks to Marc Evers for simplifying the text.

Enjoy!