<?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: Breaking the routine in Daily Scrum meetings</title>
	<atom:link href="http://www.njamin.org/blog/scrum/breaking-the-routine-in-daily-scrum-meetings-185.php/feed" rel="self" type="application/rss+xml" />
	<link>http://www.njamin.org/blog/scrum/breaking-the-routine-in-daily-scrum-meetings-185.php</link>
	<description></description>
	<lastBuildDate>Sun, 07 Feb 2010 20:21:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Marta Padilla</title>
		<link>http://www.njamin.org/blog/scrum/breaking-the-routine-in-daily-scrum-meetings-185.php/comment-page-1#comment-2006</link>
		<dc:creator>Marta Padilla</dc:creator>
		<pubDate>Fri, 10 Jul 2009 16:24:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.njamin.org/blog/?p=185#comment-2006</guid>
		<description>Hello from Spain, Nathan.

I am following your blog with great interest! Good job.
Anyway, I thought I might share here what I did in my last project as Scrum Master when the daily stand ups got a little boring.

1- Subdivide people into projects. When later we decided to merge teams, we spent a couple of weeks with common stand ups so people could start familiarising with the other project. But, normally, have daily scrums with people who work in a common thing only! and focus the updates on common ground.

2 - We decided to &quot;limit&quot; the time a person can talk. That does not mean not to raise concerns, for example. Cover what needs to be covered. But people need to learn to be focused and explain WITH FEW WORDS the 3 &quot;lines&quot;: what I have done - what I will do - blockers. Keep it simple.

And 3- Add some &quot;fun&quot; if necessary. Try to add a joke and encourage people to do so if applicable. That is, if for example you are going on holidays, say &quot;and tomorrow I won&#039;t be in the office but as I am going to Belgium I promise to bring some chocolates.&quot;

Hope it helps!
Marta</description>
		<content:encoded><![CDATA[<p>Hello from Spain, Nathan.</p>
<p>I am following your blog with great interest! Good job.<br />
Anyway, I thought I might share here what I did in my last project as Scrum Master when the daily stand ups got a little boring.</p>
<p>1- Subdivide people into projects. When later we decided to merge teams, we spent a couple of weeks with common stand ups so people could start familiarising with the other project. But, normally, have daily scrums with people who work in a common thing only! and focus the updates on common ground.</p>
<p>2 &#8211; We decided to &#8220;limit&#8221; the time a person can talk. That does not mean not to raise concerns, for example. Cover what needs to be covered. But people need to learn to be focused and explain WITH FEW WORDS the 3 &#8220;lines&#8221;: what I have done &#8211; what I will do &#8211; blockers. Keep it simple.</p>
<p>And 3- Add some &#8220;fun&#8221; if necessary. Try to add a joke and encourage people to do so if applicable. That is, if for example you are going on holidays, say &#8220;and tomorrow I won&#8217;t be in the office but as I am going to Belgium I promise to bring some chocolates.&#8221;</p>
<p>Hope it helps!<br />
Marta</p>
]]></content:encoded>
	</item>
</channel>
</rss>
