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…

The Caring and Respectful Product Owner

While reflecting on my recent activities, I started to recognise an interesting pattern regarding the role of the Product Owner. I’ve seen many of them coming from different parts of the organisations: form product management, from various levels of management, from system architecture or senior programmers. Because of the different skill sets they have, the … Read more…

Warning: Fear might twist your perception

I attended recently a meeting of project managers where “agile methods” was the subject of the evening. In fact, the whole evening was about Scrum, with three presentations trying to frame Scrum as a project management method. On one side it was good to see Scrum getting visibile to an audience that normally reasons in … Read more…

Coaching Teams, remotely

So the definition of done of a Scrum team is sick and you, dear agile coach, are intervening on the team to get them to fix it. Easy, isn’t it? Either you tackle the issue during a retrospective or on in ad-hoc discussion, point out the symptoms, ask the team how they plan to fix … Read more…