<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tea-Driven Development &#187; retrospective</title>
	<atom:link href="http://blog.mattwynne.net/tag/retrospective/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mattwynne.net</link>
	<description>Matt Wynne taking it one tea at a time</description>
	<lastBuildDate>Tue, 10 Jan 2012 20:07:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Retrospective: The Clue is in the Name</title>
		<link>http://blog.mattwynne.net/2008/01/13/remember-to-look-backwards-at-a-retrospective/</link>
		<comments>http://blog.mattwynne.net/2008/01/13/remember-to-look-backwards-at-a-retrospective/#comments</comments>
		<pubDate>Sun, 13 Jan 2008 19:47:57 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[Agile / Lean Software Development]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[lean]]></category>
		<category><![CDATA[retrospective]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[team]]></category>
		<category><![CDATA[teambuilding]]></category>
		<category><![CDATA[waste]]></category>

		<guid isPermaLink="false">http://blog.mattwynne.net/2008/01/13/remember-to-look-backwards-at-a-retrospective/</guid>
		<description><![CDATA[I facilitated our regular end-of-iteration retrospective last week, and although the feedback from the team was positive, I was left with a feeling that something wasn&#8217;t right. With our second major live release looming large on the horizon, I focussed the session on the theme of &#8216;Success&#8217;. My aim was to give the team a [...]]]></description>
			<content:encoded><![CDATA[<p>I facilitated our regular end-of-iteration retrospective last week, and although the feedback from the team was positive, I was left with a feeling that something wasn&#8217;t right.</p>

<p>With our second major live release looming large on the horizon, I focussed the session on the theme of &#8216;Success&#8217;. My aim was to give the team a blueprint for a successful iteration to keep in mind when things were tough, and to help ensure that we were all pulling in the same direction by agreeing as a team what constitutes success for us.</p>

<p><span id="more-30"></span></p>

<p>I started by asking the team to score how successful, in their own mind, the last iteration had been, drawing a histogram on the flipchart of the results. Interestingly, there was quite a variance in the scores, with most people either grading the iteration 2/5 or 4/5, perhaps suggesting that different members of the team have different criteria for success, or that they just experienced the iteration differently.</p>

<p>I then asked them to reflect on the criteria they&#8217;d used to make that judgement, again in their own mind, capturing each of the criteria on a separate index card. We then spread the cards out on the floor, and mapped them into headings: teamwork, stability, delivery, happiness &amp; joy&#8230; and a couple of others I can&#8217;t remember right now.</p>

<p>We then decided that our output would be some kind of vision statement under each heading, of the form &#8220;An iteration is a success when&#8230;&#8221; and worked through the various headings, discussing what it was that made us successful, and distilling that discussion into a bullet point on the chart.</p>

<p>Reflecting on what we&#8217;d covered, it seems to me that while the session was fun, motivating and affirming for the team, and thus valuable in it&#8217;s own way, it didn&#8217;t really enable us to focus on the major issues that are affecting us right now, such as the disruption of the recent office move. It also didn&#8217;t leave us with any concrete actions to take away and do in order to make things better. In terms of inspect and adapt, it really didn&#8217;t deliver.</p>

<p>When planning your retrospectives always remember your key goals (in priority order):</p>

<ol>
<li>Try to smoke out the most significant areas of <a href="http://www.shmula.com/223/what-is-waste">waste</a> in the team&#8217;s production of quality software</li>
<li>Invent concrete actions you can take in order to reduce this waste</li>
<li>Build and motivate the team</li>
</ol>

<p>Whilst building and motivating the team is an important goal for a session like this, it&#8217;s often a side-effect of successfully satisfying the first two. Concentrate on facilitating a session that helps reduce waste while having fun, and you&#8217;ve hit the nail on the head.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mattwynne.net/2008/01/13/remember-to-look-backwards-at-a-retrospective/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

