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…

Soft Skills Essentials at the Turku Agile Day

Here are the slides of today’s keynote I delivered together with Mike Sutton (@mhsutton) at the Turku Agile Day to a very engaged audience: thank you for the fun! Soft Skills Essentials for Software Craftsmen – Turku Agile Day 2011 from Pierluigi Pugliese  For the bibliography, please refer to this post…

Evolving Identities

In the previous post I was mentioning that a company culture is anyway emergent and what emerges cannot really be predicted, but can be influenced in many different ways. Here’s one way to do that, which I found very useful when working with agile teams. A big part of the agility is based on values … Read more…