Comments on: Retrospectives are not the only place for continual improvement http://www.thekua.com/atwork/2009/02/retrospectives-are-not-the-only-place-for-continual-improvement/ thekua's reflections on work related topics Wed, 28 Jul 2010 02:22:50 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Nick Oostvogels http://www.thekua.com/atwork/2009/02/retrospectives-are-not-the-only-place-for-continual-improvement/comment-page-1/#comment-55547 Nick Oostvogels Tue, 10 Mar 2009 12:24:07 +0000 http://www.thekua.com/atwork/?p=404#comment-55547 I've seen my previous team evolve from 'holding back improvement suggestions until the retrospective' to 'raising them the minute they appear in their mind'. My feeling says this change in mindset comes with hands-on experience. Most experienced agile developers I know, are already in this mindset, and practice continuous improvement constantly. I’ve seen my previous team evolve from ‘holding back improvement suggestions until the retrospective’ to ‘raising them the minute they appear in their mind’. My feeling says this change in mindset comes with hands-on experience. Most experienced agile developers I know, are already in this mindset, and practice continuous improvement constantly.

]]> By: Sumeet http://www.thekua.com/atwork/2009/02/retrospectives-are-not-the-only-place-for-continual-improvement/comment-page-1/#comment-53000 Sumeet Sat, 21 Feb 2009 19:05:39 +0000 http://www.thekua.com/atwork/?p=404#comment-53000 Great post Pat. I think one of the times that retros go wrong, are when people wait until the retro to make a point. If this is an issue the team hasn't ever discussed, it becomes a winge fest! I find this to be less of a problem with retros and more a problem with the culture of the team, where issues aren't big and visible and feedback isn't shared regularly. I completely agree that leaders have a great responsibility in ensuring that there are open channels of communication - retro or not! Great post Pat. I think one of the times that retros go wrong, are when people wait until the retro to make a point. If this is an issue the team hasn’t ever discussed, it becomes a winge fest!

I find this to be less of a problem with retros and more a problem with the culture of the team, where issues aren’t big and visible and feedback isn’t shared regularly. I completely agree that leaders have a great responsibility in ensuring that there are open channels of communication – retro or not!

]]>