<?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>Richard Lawrence &#187; daily Scrum</title>
	<atom:link href="http://www.richardlawrence.info/tag/daily-scrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.richardlawrence.info</link>
	<description>On making software teams happier and more productive</description>
	<lastBuildDate>Fri, 27 Jan 2012 18:41:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>7 Tips for a More Effective Daily Scrum</title>
		<link>http://www.richardlawrence.info/2009/02/07/7-tips-for-a-more-effective-daily-scrum/</link>
		<comments>http://www.richardlawrence.info/2009/02/07/7-tips-for-a-more-effective-daily-scrum/#comments</comments>
		<pubDate>Sat, 07 Feb 2009 17:40:26 +0000</pubDate>
		<dc:creator>Richard Lawrence</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[daily Scrum]]></category>
		<category><![CDATA[Scrum]]></category>

		<guid isPermaLink="false">http://www.richardlawrence.info/?p=133</guid>
		<description><![CDATA[The main purpose of the Daily Scrum is for team members to make and follow-up on commitments to one another that work towards the team&#8217;s shared sprint commitment. If your Daily Scrum has become unfocused, too long, or otherwise ineffective, here are seven ways to get it back on track. 1. Do it around the [...]


Related posts:<ol><li><a href='http://www.richardlawrence.info/2008/07/11/one-word-can-change-your-daily-scrum/' rel='bookmark' title='Permanent Link: One Word Can Change Your Daily Scrum'>One Word Can Change Your Daily Scrum</a></li>
<li><a href='http://www.richardlawrence.info/2008/09/05/making-velocity-granular-enough/' rel='bookmark' title='Permanent Link: Making Velocity Granular Enough'>Making Velocity Granular Enough</a></li>
<li><a href='http://www.richardlawrence.info/2008/11/13/a-common-but-bad-idea/' rel='bookmark' title='Permanent Link: A Common, but Bad, Idea'>A Common, but Bad, Idea</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p></p><p>The main purpose of the Daily Scrum is for team members to make and follow-up on commitments to one another that work towards the team&#8217;s shared sprint commitment. If your Daily Scrum has become unfocused, too long, or otherwise ineffective, here are seven ways to get it back on track.</p>
<p><span id="more-133"></span></p>
<p><b>1. Do it around the task board.</b> Have team members point at stories and tasks on the task board as they talk about their work. This keeps the focus on work for the sprint and makes it obvious when the talk becomes unrelated to the sprint.</p>
<p><b>2. Change the questions.</b> In <a href="/2008/07/11/one-word-can-change-your-daily-scrum/">&#8220;One Word Can Change Your Daily Scrum&#8221;</a> I described a way I like to change the three Daily Scrum questions to focus the team on getting things done.</p>
<p><b>3. Don&#8217;t show up.</b> If your Daily Scrum has turned into a status report to the ScrumMaster, try taking a few days off. Let the team report to each other instead of you. Aaron Sanders <a href="http://aaron.sanders.name/agile/an-experiment-dont-come-to-standup-today">has more here</a>. Less dramatic ways to have the same effect are avoiding eye contact or stepping outside the circle. But sometimes dramatic is necessary to shake things up.</p>
<p><b>4. Don&#8217;t talk.</b> If you&#8217;re not taking sprint tasks, you don&#8217;t need to answer the three questions. Emphasize that by not talking at all during the Daily Scrum. Use non-verbal communication when necessary, but keep your mouth shut.</p>
<p><b>5. Use a parking lot.</b> There are legitimate things for a team to talk about in the morning that don&#8217;t fit the tightly-defined purpose of the Daily Scrum. Use a parking lot (i.e. a flip chart or section of a whiteboard) to capture those topics. Address them right after the Daily Scrum is over. You can even let team members add items to the parking lot outside of the meeting to be addressed in the next &#8220;parking lot time.&#8221; That way, they&#8217;re not trying to remember their parking lot topic when they should be paying attention to the Daily Scrum.</p>
<p><b>6. Actually stand.</b> It shouldn&#8217;t be necessary for us to stand to have a short, high-energy meeting, but it really seems to help. If your team has started sitting for the Daily Scrum and it&#8217;s running longer than 15 minutes, it might be time to try standing again. Set an example by standing for the whole meeting, and maybe ask one or two influential team members to do the same. Combining this with #1 makes it feel less awkward.</p>
<p><b>7. Pass a token.</b> <a href="http://jchyip.blogspot.com/2009/02/few-pointers-for-stand-up-tokens.html">Jason Yip describes</a> how introducing randomness and play into the Daily Scrum by tossing a ball to the next person to speak can add energy to the meeting.</p>
<p>What else have you done to keep your Daily Scrum effective? Share in the comments.</p>


<p>Related posts:<ol><li><a href='http://www.richardlawrence.info/2008/07/11/one-word-can-change-your-daily-scrum/' rel='bookmark' title='Permanent Link: One Word Can Change Your Daily Scrum'>One Word Can Change Your Daily Scrum</a></li>
<li><a href='http://www.richardlawrence.info/2008/09/05/making-velocity-granular-enough/' rel='bookmark' title='Permanent Link: Making Velocity Granular Enough'>Making Velocity Granular Enough</a></li>
<li><a href='http://www.richardlawrence.info/2008/11/13/a-common-but-bad-idea/' rel='bookmark' title='Permanent Link: A Common, but Bad, Idea'>A Common, but Bad, Idea</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.richardlawrence.info/2009/02/07/7-tips-for-a-more-effective-daily-scrum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>One Word Can Change Your Daily Scrum</title>
		<link>http://www.richardlawrence.info/2008/07/11/one-word-can-change-your-daily-scrum/</link>
		<comments>http://www.richardlawrence.info/2008/07/11/one-word-can-change-your-daily-scrum/#comments</comments>
		<pubDate>Fri, 11 Jul 2008 15:46:47 +0000</pubDate>
		<dc:creator>Richard Lawrence</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[coaching]]></category>
		<category><![CDATA[daily Scrum]]></category>
		<category><![CDATA[Scrum]]></category>

		<guid isPermaLink="false">http://www.richardlawrence.info/?p=24</guid>
		<description><![CDATA[In my experience, the daily Scrum serves two purposes: for team members to make and follow up on commitments to one another, and for team members to raise and start resolving impediments. Both these purposes are directed towards reaching the Sprint goal. I started coaching a development team in an IT department this week. Most [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p></p><p>In my experience, the daily Scrum serves two purposes:</p>
<ol>
<li> for team members to make and follow up on commitments to one another, and</li>
<li>for team members to raise and start resolving impediments.</li>
</ol>
<p>Both these purposes are directed towards reaching the Sprint goal.</p>
<p>I started coaching a development team in an IT department this week. Most of the team is officially full-time on their project, but unlike the consulting teams I often work with, no one is ever really full-time on a project. There are production apps to support, people management issues, requests for technical help from other projects, non-project meetings, and a variety of other distractions.</p>
<p>Observing this team&#8217;s daily Scrums, I noticed that they talked a lot about what they did in the past 24 hours and what they would do in the next 24. Everyone seemed busy and could account for their time. But I had a hard time connecting their busyness to the work they&#8217;d committed to do in the Sprint.</p>
<p>So, I suggested a slight change to the three questions that I learned from <a href="http://www.agileadvice.com">Mishkin Berteig</a>. Instead of answering the questions, &#8220;What did you do in the last 24 hours?&#8221; and &#8220;What will you do in the next 24?,&#8221; I had the team answer the questions, &#8220;What did you <em>complete</em> in the last 24 hours?&#8221; and &#8220;What will you <em>complete</em> in the next 24?&#8221; I recommended that they point at tasks and stories on the task board while answering the questions to keep them focused on the work for the Sprint.</p>
<p>There were some objections:</p>
<p>&#8220;But I&#8217;ll feel uncomfortable saying I&#8217;m not going to complete anything today&#8230;&#8221; To which I say, &#8220;Good. You should feel uncomfortable if you&#8217;re not helping the team follow through on its commitment for the Sprint.&#8221;</p>
<p>&#8220;But our tasks are too big to complete in a day&#8230;&#8221; &#8220;Many of them are. This will give you an incentive to make them smaller in the next Sprint, which will increase your visibility into the state of the work.&#8221;</p>
<p>Nonetheless, they agreed to try it, and I&#8217;m glad they did. The change in the daily Scrum with the new questions was striking. Conversation was more focused on their commitments. Since team members couldn&#8217;t use work from outside the project to show how busy they were, they were motivated to fight the distractions and find project tasks they could commit to. The few team members who are spread across multiple projects now can see clearly where the multi-tasking is hurting their commitments to this team.</p>
<p>If your daily Scrums seem unfocused, even though everyone has lots to talk about, consider changing the questions to change the team&#8217;s behavior. Just one word can make a big difference. Try asking each other:</p>
<ol>
<li> What did you complete since we last met?</li>
<li>What will you complete before we meet again?</li>
<li> What impediments are keeping you from completing something?</li>
</ol>


<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.richardlawrence.info/2008/07/11/one-word-can-change-your-daily-scrum/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

