2 January 2020 ยท Updated 11 January 2020

Retrospective: 2019

agile, blogging, principles

One of the advantages of agile is that there are ceremonies baked in to ensure you regularly celebrate your victories and learn from your failures. In my experience, there is a lot to be gained from completing the year, putting it in the past and moving on without bringing forward any baggage you could be carrying.

A retrospective is not a silver bullet.

I've seen many bad retrospectives that give nothing more than lip service to the process. They follow the letter of the law, but not the spirit of the law and they miss out on all of the benefits of this process.

A good retrospective should celebrate what's gone well (even when the project has been a failure) and authentically (ugh, can we lose this word in 2020?) acknowledge what didn't go well.

What went well

It is important to acknowledge what you've done well and what has worked. Allow yourself to appreciate what you've managed to achieve and how far you've come.

What didn't go so well

It is important to acknowledge what hasn't worked and what you've not done well. Be careful not to shame, judge or defend yourself. Just acknowledge that it didn't go well and the impact of having this not go well.

What improvements can be carried forward

The best improvements are incremental and specific, but in the spirit of New Year resolutions I'm going with big bold wishes. :)

Final thoughts

As I reflect on the year, it feels like a step backwards compared to previous years, like I've been put on the bench. The year is gone and I don't feel like I've achieved as much as I'm used to. Even so, there's a sense of consolidating and that I've been in a holding pattern that I'm now free to break away from. It's time to refocus and reprioritise. From here, it seems like 2020 will be a year of big change.