Monday, 31 January 2011

Agile/Scrum Retrospective Meetings - Various or Different formats or plans

This collection is most certainly not uncovering amazing and unheard of ways of doing retrospectives. To be precise Agile Retrospecives has so many activities for the different phases (as defined in the book) that you can mix and match and create many different variations.

If you are on the look out for something quick that has worked elsewhere though I hope that this small list may help you save some time.

First up is a collection of games that I have known for some time although have not tried all of them.
the Retro Wiki

Next up is a format which is not on the Retro wiki and I have done in several enironments and I have also recommended to a friend who has done it and the feedback was good.

The cool wall Retro

Tasty cupcakes was recommended to me although I was not able to find any games suitable for retros on there. Perhaps some can be adapted or activities used in other types of games could be borrowed and used in a retro. Useful site to have in the bookmarks anyway.

Multi team retrospective - this is a format I have used in two variations in different companies. Works fairly well and I'd recommend it when you have multiple teams doing very short (e.g. 1 week) iterations when it is important to keep the length short. I explain it here.

How We Do a Retrospective - Tim Wingfield explains how his team does retrospective. Looks a good approach to try, certainly slightly different combination of ideas compared to what I've seen before.

[Added in Sept 2011]
Furturespective (also Future-spective) is a way of driving possible improvement opportunities by shifting your focus into the future and then looking back from there. It is described well by Anders Laestadius here and also mentioned by PierG here however it is not exactly the way we do it in my current project. So I decided to write up a summary of the "Furturespective the way we do it" here.

Agile Links - first set for 2011

I have now missed so many weeks so there really is no point to call it weekly is there?

My collection though I believe has some very good reads in it!

How to Create Change: Don’t Help People A nice view on how to instigate change. I like the beginning of it, hopefully some day I'll read it all.

What about Chris Argyris? Luc Galoppin has written a fantastic brief on Argyris and to be honest if I had read that before I might have skipped reading those books ;)

Don’t Prioritize Features! Scott Sehlhorst claims prioritising features is a waste of time. I tend to agree with him (to an extent).

Per-Feature ROI Is (Usually) a Stupid Waste of Time Here's another view that is slightly different from most people's understanding from reading all those agile books. I like the reasoning though.

Single Piece Flow in Kanban: A How-To A video presentation by James Shore and Arlo Belshee

Tightening the Feedback Loop You can never go wrong watching Patt Kua's presentations and this one is very important - very much related to double loop.

Business-Driven EnterpriseAgility A video by net objectives (A.Shalloway and co.)