<?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: Best and worst retrospective experiences</title>
	<atom:link href="http://www.stevenlist.com/blog/2009/03/31/best-and-worst-retrospectives/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stevenlist.com/blog/2009/03/31/best-and-worst-retrospectives/</link>
	<description>Thoughts on Agile software development, facilitation, communication, and relationships in the personal and professional worlds, from Steven &#34;Doc&#34; List</description>
	<lastBuildDate>Sun, 22 Jan 2012 18:20:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Cory Foy</title>
		<link>http://www.stevenlist.com/blog/2009/03/31/best-and-worst-retrospectives/comment-page-1/#comment-400</link>
		<dc:creator>Cory Foy</dc:creator>
		<pubDate>Tue, 31 Mar 2009 14:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenlist.com/blog/?p=378#comment-400</guid>
		<description>One of the best ones was right after I started my new position. The team had just (literally two days before) come off a death march project, that had them working 14-16 hour days for 2 months. It was my second day on the job, and I pulled all of the team - Devs, Management, BAs, QA, into our large conference room. They were dealing with burnout, frustration, communication issues, unhappy people, and one or two personnel issues.

What ensued I will happily describe as magical. We literally held an 18-month retrospective in the span of about 6 hours, addressing everything from the release, to the company being sold (they were sold right in the middle of the release cycle), to outsourcing, communication and other issues. The whole team was engaged, up and active, and on their own came up with some great solutions and goals to achieve. I had posted about it here: http://www.cornetdesign.com/2008/07/agile-retrospectives.html

I find the single most important exercise to be one that requires everyone to say *something* - I usually use a variant of the &quot;Check-In&quot; pattern where I have everyone say one or two words. But having a team that even after all they had been through be willing to open up, discuss where they were, discuss where they wanted to go, and develop actionable items to get there was awesome.

Hope that helps give a good story of how things can go right with a great team.</description>
		<content:encoded><![CDATA[<p>One of the best ones was right after I started my new position. The team had just (literally two days before) come off a death march project, that had them working 14-16 hour days for 2 months. It was my second day on the job, and I pulled all of the team &#8211; Devs, Management, BAs, QA, into our large conference room. They were dealing with burnout, frustration, communication issues, unhappy people, and one or two personnel issues.</p>
<p>What ensued I will happily describe as magical. We literally held an 18-month retrospective in the span of about 6 hours, addressing everything from the release, to the company being sold (they were sold right in the middle of the release cycle), to outsourcing, communication and other issues. The whole team was engaged, up and active, and on their own came up with some great solutions and goals to achieve. I had posted about it here: <a href="http://www.cornetdesign.com/2008/07/agile-retrospectives.html" rel="nofollow">http://www.cornetdesign.com/2008/07/agile-retrospectives.html</a></p>
<p>I find the single most important exercise to be one that requires everyone to say *something* &#8211; I usually use a variant of the &#8220;Check-In&#8221; pattern where I have everyone say one or two words. But having a team that even after all they had been through be willing to open up, discuss where they were, discuss where they wanted to go, and develop actionable items to get there was awesome.</p>
<p>Hope that helps give a good story of how things can go right with a great team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc</title>
		<link>http://www.stevenlist.com/blog/2009/03/31/best-and-worst-retrospectives/comment-page-1/#comment-399</link>
		<dc:creator>Doc</dc:creator>
		<pubDate>Tue, 31 Mar 2009 12:53:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenlist.com/blog/?p=378#comment-399</guid>
		<description>Thanks for the prompt, Gerry.  I&#039;ve added another story.  I hope this will be enough to prime the pump - later I&#039;ll add more stories in a separate post.  For now, I&#039;d like to gather from others.</description>
		<content:encoded><![CDATA[<p>Thanks for the prompt, Gerry.  I&#8217;ve added another story.  I hope this will be enough to prime the pump &#8211; later I&#8217;ll add more stories in a separate post.  For now, I&#8217;d like to gather from others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerry Kirk</title>
		<link>http://www.stevenlist.com/blog/2009/03/31/best-and-worst-retrospectives/comment-page-1/#comment-398</link>
		<dc:creator>Gerry Kirk</dc:creator>
		<pubDate>Tue, 31 Mar 2009 12:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenlist.com/blog/?p=378#comment-398</guid>
		<description>Hi Doc, you might get more response if you throw up a few more examples. I know I was hoping to learn more from your experiences when I saw the link to your post on Twitter. 

@gerrykirk</description>
		<content:encoded><![CDATA[<p>Hi Doc, you might get more response if you throw up a few more examples. I know I was hoping to learn more from your experiences when I saw the link to your post on Twitter. </p>
<p>@gerrykirk</p>
]]></content:encoded>
	</item>
</channel>
</rss>

