<?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>Scrum Development Blog &#187; timebox</title>
	<atom:link href="http://blog.3back.com/tag/timebox/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.3back.com</link>
	<description>Better teams make better products.</description>
	<lastBuildDate>Fri, 21 May 2010 14:04:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Time Boxing</title>
		<link>http://blog.3back.com/scrum-industry-terms/time-boxing</link>
		<comments>http://blog.3back.com/scrum-industry-terms/time-boxing#comments</comments>
		<pubDate>Wed, 07 Apr 2010 19:01:09 +0000</pubDate>
		<dc:creator>The 3Back Team</dc:creator>
				<category><![CDATA[Scrum Terms]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[time boxing]]></category>
		<category><![CDATA[timebox]]></category>

		<guid isPermaLink="false">http://blog.3back.com/?p=382</guid>
		<description><![CDATA[Time boxing is a the closest thing in agile or scrum has to ...]]></description>
			<content:encoded><![CDATA[<p>A<strong> time box</strong> is a common practice underlying most agile processes especially, <a href="http://3back.com/scrum">Scrum</a>. <strong>Time boxing</strong> is a the closest thing in agile or scrum has to something that is a best practice. Most managers or early adopters of <a href="http://3back.com">Scrum </a>wonder what they do to create a sense of urgency and the answer is simple &#8220;Time Box&#8221;.</p>
<p>In Scrum we have 6 formal time boxed events.</p>
<ol>
<li>Releasing Planning<a href="http://blog.3back.com/wp-content/uploads/2010/04/Orange-Blue-Boxes-time-boxing.jpg"><img class="alignright size-full wp-image-383" title="agile time box" src="http://blog.3back.com/wp-content/uploads/2010/04/Orange-Blue-Boxes-time-boxing.jpg" alt="scrum time boxing" width="240" height="180" /></a></li>
<li>Sprint Planning</li>
<li>Sprint</li>
<li>Sprint Reveiw</li>
<li>Sprint Retrospectvie</li>
<li>Daily Scrum</li>
</ol>
<p>Other time boxes can be applied and should be. The purpose of the time box is to cause movement and to set an expectation that we will limit the time and energy spent in any one direction. Generally people will fall prey to taking on too much work or big amorphous work that has no discernibly edges or clarity. Our understanding is similarly fuzzy and vague.</p>
<p>We can use a time box for many things including as a guide line in how we break work down into tasks or execution. Sometimes people use time boxing as a way to avoid gold platting or excessive polishing of an item or thing.</p>
<p>Time box is a critical practice in agile / <a href="http://3back.com/scrum">scrum</a> and should be applied with care. Arbitrary time boxing can drive motivation down and should not be used as a tool to create a frenetic pace or fearful environment. Time boxing is an important tool for any good <a title="what is a scrummaster?" href="http://3back.com/scrum/certified-scrummaster-training/">scrum master</a> or facilitator.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.3back.com/scrum-industry-terms/time-boxing/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When should a sprint end?</title>
		<link>http://blog.3back.com/scrum-questions/when-should-a-sprint-end</link>
		<comments>http://blog.3back.com/scrum-questions/when-should-a-sprint-end#comments</comments>
		<pubDate>Sat, 30 Jan 2010 01:40:15 +0000</pubDate>
		<dc:creator>The 3Back Team</dc:creator>
				<category><![CDATA[Scrum Questions]]></category>
		<category><![CDATA[backlog]]></category>
		<category><![CDATA[sprint]]></category>
		<category><![CDATA[sprint planning]]></category>
		<category><![CDATA[timebox]]></category>

		<guid isPermaLink="false">http://blog.3back.com/?p=69</guid>
		<description><![CDATA[Without time-boxes we rapidly loose our sense of predictability and the amount of complexity we tackle in each bite drifts upward. ]]></description>
			<content:encoded><![CDATA[<ol>
<li>We have consumed all the work we said we would in our sprint planning</li>
<li>All of the work has been completed.</li>
<li>Both the team and the product owner agree it should end.</li>
<li>The amount of time specified for the sprint has run out</li>
</ol>
<p><strong><a rel="attachment wp-att-301" href="http://blog.3back.com/?attachment_id=301"></a></strong></p>
<p><strong>Comment</strong>: Set a time-box and stick to it. Failing to adhere to the time boxes for your sprint is a bad<a rel="attachment wp-att-74" href="http://blog.3back.com/69/scrum-questions/when-should-a-sprint-end/attachment/time-box-go-stop-inspect-adapt-150x150"><img class="alignleft size-full wp-image-74" title="time-box-go-stop-inspect-adapt-150x150" src="http://blog.3back.com/wp-content/uploads/2010/01/time-box-go-stop-inspect-adapt-150x150.png" alt="using time boxes is best practice" width="150" height="150" /></a> habit. Without time-boxes we rapidly loose our sense of predictability and the amount of complexity we tackle in each bite drifts upward. Teams become fragmented and loose cohesion. This is a strong rule but, by no means an absolute. Be smart when you vary your timebox and you really need a disciplined experience well formed team to carry this off.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.3back.com/scrum-questions/when-should-a-sprint-end/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
