Inspect and adapt how you build as well as what you build

The need to inspect and adapt is the fundamental concept at the centre of the agile software development movement. However, it often seems that the drive to inspect and adapt is only deliberately applied to what we build and not how we build. This means how a team works together, how they use the technologies at their disposal and how they apply processes can go unimproved.

Retrospective Activity: By The Numbers

Introduction I thought I’d share a sprint retrospective activity I came up with recently. As I outlined in a previous post, I like to structure the retrospectives I facilitate in the form popularised by Esther Derby and Diana Larsen in their book Agile Retrospectives. That structure has five sections, each with a specific goal: Set the... Continue Reading →

The Art of the Retrospective on InfoQ

Last year I gave a talk about retrospective meetings at Agile Cambridge 2013 - a conference for Agile and Lean practitioners in the East of England. My session was called "The Art of the Retrospective" and was focused squarely on sprint retrospective meetings. The 90-minute presentation (!) tried to answer why these regular meetings are... Continue Reading →

Create tangible retrospective actions

In my view, the drive to inspect and adapt is the most important concept to have been popularized by the agile software development movement. It's an idea that got me hugely excited and engaged in the subject when I first came across it in 2005. This essence of this is that 'we will always know... Continue Reading →

Website Powered by

Up ↑