<?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>Jason Little &#187; Daily Scrum Tip</title>
	<atom:link href="http://www.agilecoach.ca/tag/daily-scrum-tip/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agilecoach.ca</link>
	<description>Changing the World, One Person at a Time</description>
	<lastBuildDate>Wed, 01 Feb 2012 15:43:12 +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>The Importance of Time-boxing</title>
		<link>http://www.agilecoach.ca/2008/08/07/the-importance-of-time-boxing/</link>
		<comments>http://www.agilecoach.ca/2008/08/07/the-importance-of-time-boxing/#comments</comments>
		<pubDate>Fri, 08 Aug 2008 00:09:08 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Daily Scrum Tip]]></category>
		<category><![CDATA[Scrum Tools]]></category>

		<guid isPermaLink="false">http://www.agilecoach.ca/2008/08/07/the-importance-of-time-boxing/</guid>
		<description><![CDATA[When using Scrum, your iterations are fixed time (1 week, 2 weeks, 30 days etc) and therefore your cost is fixed so the only thing that can vary is scope.  Time-boxing is critical to success when implementing Scrum since you don&#8217;t really want to waste a lot of time in useless or long discussions.  Yesterday [...]]]></description>
			<content:encoded><![CDATA[<p>When using Scrum, your iterations are fixed time (1 week, 2 weeks, 30 days etc) and therefore your cost is fixed so the only thing that can vary is scope.  Time-boxing is critical to success when implementing Scrum since you don&#8217;t really want to waste a lot of time in useless or long discussions.  <a href="http://plog.jasonlittle.ca/2008/08/06/when-story-estimation-sessions-go-bad/" target="_blank">Yesterday I posted</a> about an estimation session that went off the rails pretty quickly and it was due to the fact we (well, &#8220;I&#8221;) dropped the ball on enforcing the time-box rule.  We started strong and finished weak.  A stop-watch, wall clock, phone/pda or whatever is fine to use.  I like to use this <a href="http://timberfrog.com/countdown/" target="_blank">online tool</a>.  You can set the timer for whatever interval you want and it&#8217;ll beep when your time is up.  I typically give warnings at 5 minutes to go and 2 minutes to wrap it up.</p>
<p>Our iterations are 1 week (we&#8217;re re-implementing Scrum, so the shorter the better to allow the problems to surface quickly) so we use these guidelines for time-boxing:</p>
<ul>
<li><strong>sprint backlog</strong>: <em>1.5 hours</em> &#8211; this is where the team commits to their work and break stories into tasks.</li>
<li><strong>development activities</strong>:  <em>1 hour</em> -  If you&#8217;re stuck after an hour, ask a team member</li>
<li><strong>&#8216;stop the line&#8217; discussions:</strong>  <em>15 minutes</em> -if a team members runs into a roadblock, the whole team stops and a quick 15 minute brainstorm session happens.  All potential solutions are written on the whiteboard and then the line resumes work.</li>
</ul>
<p>The biggest question the team always has around time-boxing is &#8220;what happens if the meeting is over and we haven&#8217;t finished our task breakout?&#8221;  The answer is simple:  The meeting is over.  If you didn&#8217;t meet your goal, schedule another discussion or in this case, when it comes time to work on that story, time-box the task breakout to 15 minutes.</p>
<p>The lesson is, by time-boxing your efforts you force yourself into focusing on the issue or discussion at hand.  It&#8217;s tempting to allow a couple more minutes here and a couple more minutes there, but avoid the temptation.  The team will get into a rhythm pretty quickly and be much more efficient at time-boxing.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.agilecoach.ca/2008/08/07/the-importance-of-time-boxing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Truthfulness is the key</title>
		<link>http://www.agilecoach.ca/2008/08/06/truthfulness-is-the-key/</link>
		<comments>http://www.agilecoach.ca/2008/08/06/truthfulness-is-the-key/#comments</comments>
		<pubDate>Thu, 07 Aug 2008 01:29:13 +0000</pubDate>
		<dc:creator>Jason</dc:creator>
				<category><![CDATA[Daily Scrum Tip]]></category>

		<guid isPermaLink="false">http://www.agilecoach.ca/2008/08/06/truthfulness-is-the-key/</guid>
		<description><![CDATA[This extends to any type of business or co-worker relationship, but Scrum teaches truthfulness above all else.  The Team must trust each other and be honest with themselves and other Team members.  If you have a problem with a Team member, talk to them.  If you see a Team member struggling, help them.  Let it [...]]]></description>
			<content:encoded><![CDATA[<p>This extends to any type of business or co-worker relationship, but Scrum teaches truthfulness above all else.  The Team must trust each other and be honest with themselves and other Team members.  If you have a problem with a Team member, talk to them.  If you see a Team member struggling, help them.  Let it all hang out at the retrospective.  You can&#8217;t move forward unless you are honest.  Sounds hokey, but business is business, nothing is <u><strong>EVER </strong></u>personal.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.agilecoach.ca/2008/08/06/truthfulness-is-the-key/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

