A conflict of interests

It starts in the usual way: You’re having a discussion with somebody from your current client and he/she tells you that agile practice X is bogus/useless/… and that that person is not going to use it/apply it/promote it to others. Now… what do you do? Before you realise it, you are having a conflict of … Read more…

The retrospective: is not about you, dear facilitator!

This is the fourth article in a mini-retrospectives series. In the previous ones I wrote about how retrospectives should be done at regular intervals, but also in other occasions and how the retrospective could be done in different groups than just the team and that sometimes changes happen even without an action item being clearly … Read more…

Retrospectives: “Tunes and adjusts its behaviour accordingly”…

This is the third article in a mini-retrospectives series. In the previous ones I wrote about how retrospectives should be done at regular intervals, but also in other occasions and how the retrospective could be done in different groups than just the team. In this post I will continue to challenge the 12th principle of … Read more…

Retrospectives: “The Team reflects”… more or less?

This is the second article in a mini-retrospectives series. In the previous one I talked about how retrospectives should be done at regular intervals, but also in other occasions. In this post I will continue to challenge the 12th principle of the agile manifesto to explain other ways to spice up your retrospectives. The 12th … Read more…

Retrospectives: “At regular intervals”… or not?

This is the first in a series of posts about how to moderate retrospectives creatively. Traditionally the retrospective in agile software development is the reflection done at the end of the iteration. Principle twelve of the Agile Manifesto says “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts … Read more…

On refactoring and the organisation

I often get questions about how to approach refactoring at the cultural level, i.e. how to promote it in the organisation. This post is an adaptation of some advises I gave to a customer of mine… The best way is to have refactoring done as part of the story development, so during the sprint. It’s … Read more…

“Scaling” the team – part two

In the previous post I introduced you to Solution Focused scales and how they can be used in a one-to-one scenario. Now we’ll extend this to a team context, but first, here are some tips… Tips on using scales A constructivistic approach is important also when using scales: whatever numbers the client chooses, it must … Read more…

“Scaling” the team – part one

No, this post is not about increasing the size of your development team, but about how to establish some measurements in your team – typically during the retrospectives, but not only – to support continuous improvement: let’s talk about Solution Focused Scales. I already discussed this technique in my Solution Focus presentation, but listening to … Read more…

There is no resistance in coaching

One of the concepts I hear many colleague agile coaches talking about is the concept of “resistance” of the client. Typical sentences are “he is resisting the agile transition” or “I talked to her about X and she resisted the proposals I made”. Now here’s one thing that is important to consider: there is no … Read more…

The best way to coach a team is…

…to coach its individuals one-to-one! Contradiction? Well, some time ago I thought so as well, but… Over the last years I had a few clients where, because of some constraints in the setting I was working with, I needed to “speed up” with the coaching program and “deliver” a high-performance team faster than I usually … Read more…

Motivation: cause or effect?

In a conversation during the last agile coach camp Germany I was reminded of something I see often in agility: motivational interventions. Most, if not all, agile coaches use them in one form or another: a workshop moderated with a pot of energy on their side, a training where the reasons why agile is what … Read more…

Change, Change, Change! – Workshop at XP Days Benelux

Here are the slides I presented today at XP Days Benelux in Mechelen together with Dirk Lässig (@djlaessig): Change, Change, Change! This time in a workshop version, where the participants learned to use these conditions to design change. For a detailed description of what this is about, please refer to my previous post. Change, change, … Read more…

Innovation Needs Waste! – Workshop at XP Days Benelux 2011

Here’s a new post on design thinking. As promised in my previous post, some more details on what the presentation at XP Days Germany together with Dirk Lässig (@djlaessig) was about. In fact, we just delivered the same material in the format of a workshop at XP Days Benelux, where, rather than talking too much, … Read more…