Comments on: Retrospectives IN and ON action http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/ scattered thoughts of a wannabe thinker Fri, 25 Jul 2008 06:45:41 +0000 http://wordpress.org/?v=MU By: naisioxerloro http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-9049 naisioxerloro Wed, 28 Nov 2007 21:28:32 +0000 https://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-9049 Hi. Good design, who make it? Hi.
Good design, who make it?

]]> By: Why Business Acumen « BrainScrum http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-3355 Why Business Acumen « BrainScrum Sat, 24 Mar 2007 17:24:23 +0000 https://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-3355 [...] are supposed to apply an approach sort of “by the book” before starting to change it (through retrospectives, of course! ;-)). This is also why people talk about Shu Ha Ri as a way to approach [...] [...] are supposed to apply an approach sort of “by the book” before starting to change it (through retrospectives, of course! ;-)). This is also why people talk about Shu Ha Ri as a way to approach [...]

]]> By: Codentropy » Blog Archive » Know your Team http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-31 Codentropy » Blog Archive » Know your Team Sun, 11 Jun 2006 13:44:35 +0000 https://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-31 [...] Recently I have read an interesting Marco’s post that get the point. [...] [...] Recently I have read an interesting Marco’s post that get the point. [...]

]]> By: Codentropy » Blog Archive » Conoscere il proprio Team http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-28 Codentropy » Blog Archive » Conoscere il proprio Team Sun, 11 Jun 2006 10:09:24 +0000 https://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-28 [...] Recentemente proprio su quest’ultimo punto ho letto un interessante post di Marco. [...] [...] Recentemente proprio su quest’ultimo punto ho letto un interessante post di Marco. [...]

]]> By: Ronica R. http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-21 Ronica R. Thu, 01 Jun 2006 21:44:56 +0000 https://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-21 I also am a Scrum person. Because Scrum/agile are at their core empirical processes, learning is built in throughout. So, yes, there is a formal retrospective at the end. But there are also the daily meetings, an emphasis on an open work setting that fosters constant communication, a tendency toward many prototypings/demos/other feedback points with users. Also, each iteration provides a reflection point at the end, but really these are intermediate reflection points to the real end, which is a release. My point here is that agile processes already do provide many points of retrospective IN action. Furthermore, and I suspect this is where you are really going with this idea, practicing scrum/agile does put team members into a habit of reflection, retrospective, and learning. Therefore, team members find more opportunities for feedback and adjustment. Maybe the next question is: is there such a thing as too much retrospective IN action? Can it cause you to change course too easily, or to fail to give an idea a chance to work? Or does that very question imply an over-thinking of what is really a simple process of collaboration, which is different from real retrospective, which is what we--in scrum--do every two weeks? I also am a Scrum person. Because Scrum/agile are at their core empirical processes, learning is built in throughout. So, yes, there is a formal retrospective at the end. But there are also the daily meetings, an emphasis on an open work setting that fosters constant communication, a tendency toward many prototypings/demos/other feedback points with users. Also, each iteration provides a reflection point at the end, but really these are intermediate reflection points to the real end, which is a release.

My point here is that agile processes already do provide many points of retrospective IN action. Furthermore, and I suspect this is where you are really going with this idea, practicing scrum/agile does put team members into a habit of reflection, retrospective, and learning. Therefore, team members find more opportunities for feedback and adjustment.

Maybe the next question is: is there such a thing as too much retrospective IN action? Can it cause you to change course too easily, or to fail to give an idea a chance to work? Or does that very question imply an over-thinking of what is really a simple process of collaboration, which is different from real retrospective, which is what we–in scrum–do every two weeks?

]]> By: David H. http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-20 David H. Thu, 01 Jun 2006 21:09:41 +0000 https://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-20 Hello. I would like to say that this is a wonderful post. Since you wanted some feedback from a Scrum person, I thought I should add one thought. In a retrospective I also enjoy to reinforce the strenghts a Scrum team has shown. This could also mean that individual strenghts are shown to the team, exposed and carefully taking into account for ones own register. That means that I usually pay a lot attention to even make the "bad things" sound good. That is when "What went wrong" beacomes "What should be improved". I think it is very important to set a positive tone to all of this. Apart from that retrospectives should fit in with the work culture of the company and the team. I have also learned, that removing the team from their actual work environment helps to lighten the mood and open them up. Hello.

I would like to say that this is a wonderful post. Since you wanted some feedback from a Scrum person, I thought I should add one thought. In a retrospective I also enjoy to reinforce the strenghts a Scrum team has shown. This could also mean that individual strenghts are shown to the team, exposed and carefully taking into account for ones own register. That means that I usually pay a lot attention to even make the “bad things” sound good. That is when “What went wrong” beacomes “What should be improved”. I think it is very important to set a positive tone to all of this.

Apart from that retrospectives should fit in with the work culture of the company and the team. I have also learned, that removing the team from their actual work environment helps to lighten the mood and open them up.

]]> By: Maksim http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-19 Maksim Wed, 24 May 2006 02:59:43 +0000 https://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-19 Absolutely agree that reflection is a very important factor in building teams and continuous learning. However self reflection can sometime be misleading and may re-enforce non-productive behaviors. It's important to gather high quality 360 degree feedback, ( i.e. Clients, Developers, Sponsors, Stakeholders... ) and look at the whole picture and not the first thing that comes to mind. Absolutely agree that reflection is a very important factor in building teams and continuous learning. However self reflection can sometime be misleading and may re-enforce non-productive behaviors. It’s important to gather high quality 360 degree feedback, ( i.e. Clients, Developers, Sponsors, Stakeholders… ) and look at the whole picture and not the first thing that comes to mind.

]]> By: DJN http://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-17 DJN Tue, 23 May 2006 07:32:54 +0000 https://brainscrum.wordpress.com/2006/05/22/retrospectives-in-and-on-action/#comment-17 "Reflecting on experience provides the basis for forming more abstract ideas which can then be applied and tested in further experience. It enables us recognise new opportunities and learn from them." I agree 110%. “Reflecting on experience provides the basis for forming more abstract ideas which can then be applied and tested in further experience. It enables us recognise new opportunities and learn from them.”

I agree 110%.

]]>