me.andering

The “New New NEW! Product development game” is a simulation we are developing. Participants experience various agile planning practices, so that they can create a development strategy that fits their needs, rather than following some arbitrary rules out of a book. Last week at XP2009 we did the first public run. Here is a brief report accompanied by photos from that workshop. Continue reading ‘New new new! Product development game at XP2009′

In our quest to put into words and pictures how important context is to choose practices, to show that there is no one-size-fits all solution for process and change strategy, Marc Evers and me went on tour last year with a presentation on Cultural Patterns. Take a look over at InfoQ – Beyond Agile: Cultural Patterns.

Willem and Marc introduce cultural patterns that can be found in software organizations. By understanding the cultural patterns then you can better adapt your practices. Continue reading ‘Beyond Agile: Cultural Patterns video on InfoQ’

Jurgen Appelo writes in Communication = Information * Relationships that “top-down systems thinking is a management fad“. I agree. Systems thinking works only if it happens in all directions at once. It seems to work when a group of people is doing systems thinking  in the same room at the same time. All combined, these people bring the perspectives that are necessary to come up with changes that work. Continue reading ‘Bottom Up Systems Thinking’

The new year seems to be an excellent time to think about your time management. It seemed to be for mine, and around new year I was chatting with Marc. Marc said “I’m reading a new book on personal productivity”. That made me think. Marc is one of the most productive people I know, so why would he bother reading yet another book like that. He has many, and I knew him since before he had any of those or was into,  say methodology. Then, just like now, he is one of the most productive people I know.

“So, why bother?” I asked him.

“I’m productive, but I would like to do it with less stress”. I can understand that. And then I  thought that by thinking about more productivity and less stress, you might achieve they opposite. I’ve met some very relaxed people. Were they thinking about stress? Probably not. Not thinking about stress may be like not thinking about a banana. You’ve probably read about research where they ask people to not think about something a banana, for instance, and it turns out they think more about it when you ask them not to…

Take Getting Things Done, for instance. The book has as subtitle “the art of stress-free productivity”. I have the book, and have tried it a couple of times. To me, it seems to have too many moving parts. Even if you take just one part, it might cause you stress. For instance, Johanna Rothman just wrote how Inbox zero is hard for her. GTD states that you should end every day with an empty inbox.

I tried that a couple of times, and after a while I could not get it to work either. In the mean time, I was stressing about it, worrying that I was not working to the norm I had set myself… Thus achieving the opposite of what I set out to do.

So, before Marc got around to explaining that The art of getting everything done by putting it off to tomorrow, and the main principles are of his shiny new tool, I came to the conclusion that it might be best for me to eat my own dogfood, and apply to myself what I tend to advise to teams these days:

Reflect, find out what works for you and do more of it (and do some experiments every once in a while to see if something else would work even better).

Trying out another methodology would not work for me at the moment, because, I might be worrying if I was ‘doing it right’. Asking if you’re doing it right is often the wrong questions to ask… And following a methodology to a T might give you more stress, and thus less productivity, instead of the other way around.

So don’t think about stress, I wish you a relaxed day!

Chris Matts is drafting comic strips on real options and financial options in the new decision coach blog he and Olav Maassen started yesterday.

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.

In other news today:

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…

I wrote a teaser post about iterative and incremental rebranding of eXperience Agile in September… It’s been four months and almost as many newsletters since then . So time to de-tease the blog…

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).

Continue reading ‘A QWAN year ’

Marc Evers and I were a bit buzzed… We hoped, this year, to start announcing agile open earlier (and, unlike last year, not keep repeating ‘we should get started’). Well, unlike last year, we didn’t keep repeating it. We just didn’t get round tuit…

So last week, we finally got together around a whiteboard, decided that we did want to hold it in June (like last year, and as we planned), but we didn’t have a location etc. and didn’t want to spend as much time as last year in sending out invoices, dealing with exceptions etc.

So, we decided to go with an affordable conference location and leave things like hotel, dinner out of the basic package. That means we can send out just one type of invoice – you come two days, or you don’t, and  beside diet preferences there are no options. Well, you can of course volunteer (we got spontaneous offers for that. ) or sponsor.  We also decided to cap the conference at just thirty participants, so we could go with the venue. One of the reasons being, we thought we can’t get that many participants in a month anyway… Surprise, surprise, sending out the invite to a couple of mailinglists, and we’ve already passed the twenty participants mark. And we have some sponsors as well (we didn’t expect many in this timeframe, so we’re pleasantly surprised. Now we have to make sponsor packages and facilitate the other volunteers so we can self-organize )

So, without much further ado, I’m proud to announce the next

Agile Open Europe 2008

will take place in Utrecht, NL on June 5th and 6th. A vibrant place to push the envelope and do business together. And yes, we will find Belgian Beer – one participant listed that as a dietary requirement   Looks like its’ going to be good fun again. See you there!

And if you ’still’ haven’t registered – there’s a handful of places left…

Have you been involved in an ‘agile transition’ (or some other form of process improvement)?
Have your co-workers complained there was not enough process?
Have your co-workers complained there was too much process?
Continue reading ‘Beyond Agile?’

Marc and I finished translating Belofte maakt schuld to English, we proudly present: Promise is Debt.  In this case study, based on our own stories, we apply systems thinking to a common destructive behaviour pattern in IT organisations: overpromise when you underdeliver, and then overpromise some more…

So far we had a good response on  Belofte maakt schuld, overpromising and underdelivering seems to be even more common than we thought.

Writing papers in two languages is an experiment for me, usually I write in English, and I used to write in Dutch when I was writing articles for Dutch IT magazines. Writing and editing a translation gives me a fresh perspective on the text, and in the meantime I’ve had some more discussions on the topic. In the end, I came to the conclusion that if you really want accurate estimates, and stop overpromising, you have to foster a culture where saying no is ok.