<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Retrospectives: Some thoughts</title>
	<atom:link href="http://www.markhneedham.com/blog/2010/06/10/retrospectives-some-thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2010/06/10/retrospectives-some-thoughts/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Writing off a badly executed practice at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2010/06/10/retrospectives-some-thoughts/comment-page-1/#comment-41733</link>
		<dc:creator>Writing off a badly executed practice at Mark Needham</dc:creator>
		<pubDate>Sat, 17 Jul 2010 17:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=2472#comment-41733</guid>
		<description>[...] example I wrote a post about a month ago outlining some of the problems that we&#039;d been having with retrospec... on some of the projects that I&#039;ve been working on and at one stage towards the beginning of the [...]</description>
		<content:encoded><![CDATA[<p>[...] example I wrote a post about a month ago outlining some of the problems that we&#039;d been having with retrospec&#8230; on some of the projects that I&#039;ve been working on and at one stage towards the beginning of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2010/06/10/retrospectives-some-thoughts/comment-page-1/#comment-38992</link>
		<dc:creator>Mark Needham</dc:creator>
		<pubDate>Thu, 10 Jun 2010 16:53:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=2472#comment-38992</guid>
		<description>@Andre - ah cool I haven&#039;t read the Prag book on Retrospectives, I think that&#039;s gotta be one for me to look at now! 

Have you read the Kerth one by the way? Heard that one&#039;s meant to be good although I haven&#039;t read it either.

I like the ideas for 5 why&#039;s/root cause analysis - that sounds like a cool way to make a retro a bit less boring.

Somehow never thought of that - thanks for the tips!</description>
		<content:encoded><![CDATA[<p>@Andre &#8211; ah cool I haven&#8217;t read the Prag book on Retrospectives, I think that&#8217;s gotta be one for me to look at now! </p>
<p>Have you read the Kerth one by the way? Heard that one&#8217;s meant to be good although I haven&#8217;t read it either.</p>
<p>I like the ideas for 5 why&#8217;s/root cause analysis &#8211; that sounds like a cool way to make a retro a bit less boring.</p>
<p>Somehow never thought of that &#8211; thanks for the tips!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: André Faria Gomes</title>
		<link>http://www.markhneedham.com/blog/2010/06/10/retrospectives-some-thoughts/comment-page-1/#comment-38991</link>
		<dc:creator>André Faria Gomes</dc:creator>
		<pubDate>Thu, 10 Jun 2010 16:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=2472#comment-38991</guid>
		<description>Really Nice ,Needham! Here at Bluesoft in Brazil we have weekly retrospectives at the very end of each sprint, and we also have a space in our kanban for things do improve (or not so nice events), things that went well, and ideas. We use postits for each item.

We lived a moment in the past like you described when the team were demotivated to have retrospectives meetings because the subjects were always the same, but then after reading the Diana&#039;s Book from the pragmatic programmers, we started to use some techniques that really helped us out. 

Things like:
- Taking the bugs and make a root cause analysis.
- Taking the last potencial problems and apply the 5 whys (lean).
- The 5 hats of thinking technique
- The brainstorming and filtering from the Art of Agile Book</description>
		<content:encoded><![CDATA[<p>Really Nice ,Needham! Here at Bluesoft in Brazil we have weekly retrospectives at the very end of each sprint, and we also have a space in our kanban for things do improve (or not so nice events), things that went well, and ideas. We use postits for each item.</p>
<p>We lived a moment in the past like you described when the team were demotivated to have retrospectives meetings because the subjects were always the same, but then after reading the Diana&#8217;s Book from the pragmatic programmers, we started to use some techniques that really helped us out. </p>
<p>Things like:<br />
- Taking the bugs and make a root cause analysis.<br />
- Taking the last potencial problems and apply the 5 whys (lean).<br />
- The 5 hats of thinking technique<br />
- The brainstorming and filtering from the Art of Agile Book</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Retrospectives: Some thoughts at Mark Needham -- Topsy.com</title>
		<link>http://www.markhneedham.com/blog/2010/06/10/retrospectives-some-thoughts/comment-page-1/#comment-38988</link>
		<dc:creator>Tweets that mention Retrospectives: Some thoughts at Mark Needham -- Topsy.com</dc:creator>
		<pubDate>Thu, 10 Jun 2010 14:36:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=2472#comment-38988</guid>
		<description>[...] This post was mentioned on Twitter by Arnon Rotem-Gal-Oz, Bruce Onder. Bruce Onder said: Mark Needham: Retrospectives: Some thoughts http://ff.im/-lNP6V [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Arnon Rotem-Gal-Oz, Bruce Onder. Bruce Onder said: Mark Needham: Retrospectives: Some thoughts <a href="http://ff.im/-lNP6V" rel="nofollow">http://ff.im/-lNP6V</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jussi Mononen</title>
		<link>http://www.markhneedham.com/blog/2010/06/10/retrospectives-some-thoughts/comment-page-1/#comment-38980</link>
		<dc:creator>Jussi Mononen</dc:creator>
		<pubDate>Thu, 10 Jun 2010 11:00:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=2472#comment-38980</guid>
		<description>Hi,

IMO retros should never be skipped either. It is very easy to feel that they do not bring any value but then I would start wondering whether the retrospectives are facilitated properly. Good ideas can be found in the Agile Retrospectives book (http://pragprog.com/titles/dlret/agile-retrospectives) or with the help of Dr. Google.

Bring in a facilitator from outside, someone outside the team. Retrospectives are the most important part of Scrum, it is the only place where you can inspect and adapt. Skip it, and you&#039;ll be doomed to stagnation (or at least you will have hard time of improving the ways you work) :-)</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>IMO retros should never be skipped either. It is very easy to feel that they do not bring any value but then I would start wondering whether the retrospectives are facilitated properly. Good ideas can be found in the Agile Retrospectives book (<a href="http://pragprog.com/titles/dlret/agile-retrospectives" rel="nofollow">http://pragprog.com/titles/dlret/agile-retrospectives</a>) or with the help of Dr. Google.</p>
<p>Bring in a facilitator from outside, someone outside the team. Retrospectives are the most important part of Scrum, it is the only place where you can inspect and adapt. Skip it, and you&#8217;ll be doomed to stagnation (or at least you will have hard time of improving the ways you work) <img src='http://www.markhneedham.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

