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 )

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.

“I could go on. I see much commonality among the Agile methods, and I think there would be more were there not so much advantage — or perceived advantage — to having a brand of one’s own. It would also be helpful if a few of us egomaniacs populating the upper tiers of the Agile thought space were able to follow our own dictates and communicate effectively with each other. ”

I believe branding is overrated. Branding makes me think of what cowboys do with cows – mark them with a hot iron to show which farm owns them. I prefer not to see my clients as cows, and I do not believe people want to be owned by a methodology farm either…
Here’s what Merriam Webster said when I searched for branding:

“One entry found for brand.

Main Entry: ²brand
Function: transitive verb
1 : to mark with a brand
2 : to mark with disapproval : STIGMATIZE
3 : to impress indelibly <brand the lesson on his mind>
- brand·er noun”

Dutch also has the word branding. It means washing, as in waves washing the shore… As far as impact of branding for consultants goes – shores have the tendency to move slowly, even here in Holland where shores tend to wash away sometimes.

(I’m deliberately ignoring the communication remark in Ron’s quote. I’m puzzling on that, I hope you are too).