Archive for the 'people & systems' Category

Page 3 of 24

XP2009 – workshops and tutorials kick ass by the sea

I haven’t gone to XP200* for a while. This year is different :)   It has a very strong programme with an excellent balance between practitioner workshops and tutorials and a more focused academic track. Amongst other things, sessions by agile regulars like Jeff Patton on User Story Mapping, David Anderson on Kanban, the Poppendiecks on Lean, Diana Larsen on Retrospectives, Steve Freeman on Mocks, american Mike Hill on CRRAP as well as  workshops by  people you may not yet have heard about: the Scrum Board Game by Wim van de Goor and Stefan van den Oord looked like a lot of fun at the last XP Days Benelux, and the Agile Analysis tutorial by Joke Vandemaele should be very good as well – she is part of a ‘new wave’ of what I call example driven business analysts (a shorter version will also run at mini XP Days in Mechelen, May 11). And there is an Open Space of course, for the latest and greatest insights and the most difficult of problems.

It’s back in Sardinia, in the beautiful town of Pula so the place itself is worth a visit – I was in Sardinia once for XP2001 – it is stunning.

looking to the Sea from Pula fourtress by Alistair Young

Temple of Augustus, Pula by yellow book ltd.

Temple of Augustus, Pula by yellow book ltd

Sunset in Pula by toucego.
Sunset in Pula by Nelson Martin
I’m going to xp2009 learn from the best, and make some photos of my own. I look forward to meeting you there!

SPA 2009 was wicked: Haskell, Beatboxing and Anarchy in the UK

Spa 2009 was an experience grenade, I am somewhat recovered from the blast I had there, but not quite, so here are some impressions and photos.

Haskell

This years’ conference had many sessions on a hitherto rather obscure programming language: Haskell. I knew the guys from the Paris CodingDojo (at the very least EmmanuelGaillot, ChristopheThibaut and ArnaudBailly ) have been jamming on Haskell for a while, I was surprised to learn Ivan Moore and Mike Hill, this years’ programme chairs also have taken an interest in it.

I am not exactly sure why. Continue reading ‘SPA 2009 was wicked: Haskell, Beatboxing and Anarchy in the UK’

Conference workshops – the second quarter

A bit late, as the first conference – SPA2009 – has already passed :) . It was great, more about that later. We already put the write-up for Consulting Without Secrets up on the SPA wiki, Sea Stories and Fairy tales is yet to follow. Continue reading ‘Conference workshops – the second quarter’

Bottom Up Systems Thinking

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’

Don’t Stop Thinking about Naming

Steve Freeman did a great writeup of the session Marc Evers and I hosted at the Software Craftsmanship Conference: Mock Roles not Objects, live and in person.

What can I add besides a big thank you, especially since Steve asked for feedback before posting and incorporated a comment about my habitual way of going about naming – creating a bit more code on an empty system and then go mad about naming after I have something more to generalize on.

A few things:

Continue reading ‘Don’t Stop Thinking about Naming’

Agile Open France proceedings online

Raphaël Pierquin has scanned the first batch of session notes from Agile Open France.
Some of the attendees are excellent (visual) note takers – even notes of sessions I did not attend speak to me. Enjoy (works best if you can read a bit of French, although the glyphs also speak volumes)

Agile Open France – refreshingly simple

Does this look like a place of work to you?

Hotel Arnold at dawn

Hotel Arnold at dawn

To me neither. This was my place of work for three days during Agile Open France.  The effect it has on me is hard to explain, I hope the pictures help paint a clearer eh, picture.

Continue reading ‘Agile Open France – refreshingly simple’

Don’t think of a banana stress…

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!

Responsibility Driven Design at Software Craftsmanship Conference

Marc and I just got word from Jason Gorman, that our session Responsibility Driven Design with Mock Objects has been accepted for the conference that has outlawed index cards, post-its and lego: the Software Craftsmanship Conference in London, February 26.

The year is getting off to a good start – we did an iteration on the session proposal January 1st. To fit with the spirit of the conference, we’ve added a coders’ dojo to it. I look forward to going back to the BBC site, having facilitated in-house dojos before.

I’m still wondering what happened with our other proposal – the continuous integration install party. It might not have gotten through, but I guess we could run it as a BoF (possibly at the SPA conference in April, also in london).

Financial Options for noobs

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.