Comments on: Some Thoughts on Agile Retrospectives http://www.njamin.org/blog/scrum/some-thoughts-on-agile-retrospectives-53.php Sun, 07 Feb 2010 20:21:04 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Radar at Ricardo Mestre’s Blog http://www.njamin.org/blog/scrum/some-thoughts-on-agile-retrospectives-53.php/comment-page-1#comment-1163 Radar at Ricardo Mestre’s Blog Thu, 16 Oct 2008 13:11:27 +0000 http://www.njamin.org/blog/?p=53#comment-1163 [...] Interesting post from Nathan Jamin, regarding Retrospectives in Distributed Scrum Teams [...] [...] Interesting post from Nathan Jamin, regarding Retrospectives in Distributed Scrum Teams [...]

]]> By: David McLean http://www.njamin.org/blog/scrum/some-thoughts-on-agile-retrospectives-53.php/comment-page-1#comment-121 David McLean Wed, 18 Jun 2008 06:39:20 +0000 http://www.njamin.org/blog/?p=53#comment-121 Nathan - thanks for the mention. I'm trying to set aside retrospective days where there are series of meetings throughout the day where various aspects of retrospective are attended to - and delegating preparation to various members of the team - rather than just an hour or two. I've got an idea for you that is great for stimulating any retrospective - and particularly for distributed teams - peer review league table. It needs to be done with sensitivity but the point is to ensure you have good peer review going on in the first place then get someone to select 3 good reviews and 3 bad reviews. Open these for debate in the retrospective and get the team to vote for the champion and wooden spoon reviews. Years ago I had a guy who copied and pasted the same piece of code 32 times with one variable value changed in each - from there on it was known as his 32 bit code - and he never did it again. Occasionally this creates some friction and raises strong opinions - so long as no blood is drawn its quite healthy over all :) Nathan – thanks for the mention.

I’m trying to set aside retrospective days where there are series of meetings throughout the day where various aspects of retrospective are attended to – and delegating preparation to various members of the team – rather than just an hour or two.

I’ve got an idea for you that is great for stimulating any retrospective – and particularly for distributed teams – peer review league table.

It needs to be done with sensitivity but the point is to ensure you have good peer review going on in the first place then get someone to select 3 good reviews and 3 bad reviews. Open these for debate in the retrospective and get the team to vote for the champion and wooden spoon reviews. Years ago I had a guy who copied and pasted the same piece of code 32 times with one variable value changed in each – from there on it was known as his 32 bit code – and he never did it again. Occasionally this creates some friction and raises strong opinions – so long as no blood is drawn its quite healthy over all :)

]]>