<?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"
	>
<channel>
	<title>Comments on: When You&#8217;re in Chaos, Try Baby Steps</title>
	<atom:link href="http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html/feed" rel="self" type="application/rss+xml" />
	<link>http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html</link>
	<description>Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk.</description>
	<pubDate>Mon, 08 Sep 2008 06:41:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Pete</title>
		<link>http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html#comment-6188</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Thu, 03 Apr 2008 05:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html#comment-6188</guid>
		<description>This is an excellent approach to address this specific problem, one which I use myself and recommend to clients as well. I find that apart from focusing the team it allows me to track progress using activities short enough to allow me to use the 'done/not done' approach. It means that I don't get stuck in the never-ending '90% complete' rut and my progress reports are based on real metrics (number of tasks completed vs number of tasks remaining to complete a feature - combined with task complexity and team velocity) and not the team members' perceptions of what complete means. Great post Johanna!</description>
		<content:encoded><![CDATA[<p>This is an excellent approach to address this specific problem, one which I use myself and recommend to clients as well. I find that apart from focusing the team it allows me to track progress using activities short enough to allow me to use the &#8216;done/not done&#8217; approach. It means that I don&#8217;t get stuck in the never-ending &#8216;90% complete&#8217; rut and my progress reports are based on real metrics (number of tasks completed vs number of tasks remaining to complete a feature - combined with task complexity and team velocity) and not the team members&#8217; perceptions of what complete means. Great post Johanna!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay, writer Memberspeed.com</title>
		<link>http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html#comment-5519</link>
		<dc:creator>Jay, writer Memberspeed.com</dc:creator>
		<pubDate>Wed, 12 Mar 2008 03:25:27 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html#comment-5519</guid>
		<description>This actually reminds me of a Gantt Chart. It's the chart we use for our thesis-writing process. We need to follow each month's schedule properly or else we'll get sidetracked and be delayed. If I'm not mistaken, the schedule is divided into weeks as well.</description>
		<content:encoded><![CDATA[<p>This actually reminds me of a Gantt Chart. It&#8217;s the chart we use for our thesis-writing process. We need to follow each month&#8217;s schedule properly or else we&#8217;ll get sidetracked and be delayed. If I&#8217;m not mistaken, the schedule is divided into weeks as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html#comment-5171</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 04 Mar 2008 21:59:25 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html#comment-5171</guid>
		<description>I would add that when progress seems to have stopped, it's important to have absolutely unambigous goals.  I remember a former manager who asked us all "Which things are 100% done and which are not?"  We'd gotten bogged down with lots of "nearly complete" tasks. The baby step approach probably automatically defines unambiguous goals.  Some of the benefit may come from the clarity of the goal as well as its small size.</description>
		<content:encoded><![CDATA[<p>I would add that when progress seems to have stopped, it&#8217;s important to have absolutely unambigous goals.  I remember a former manager who asked us all &#8220;Which things are 100% done and which are not?&#8221;  We&#8217;d gotten bogged down with lots of &#8220;nearly complete&#8221; tasks. The baby step approach probably automatically defines unambiguous goals.  Some of the benefit may come from the clarity of the goal as well as its small size.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Christiansen</title>
		<link>http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html#comment-5161</link>
		<dc:creator>David Christiansen</dc:creator>
		<pubDate>Tue, 04 Mar 2008 18:19:51 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/2008/03/when-youre-in-chaos-try-baby-steps.html#comment-5161</guid>
		<description>I think some project managers think the one-week timebox approach is too much work. It is definitely a high-energy approach that requires the ability to re-focus at will, but I don't think the overhead is as high as many people believe. It's certainly less effort than plan management based on comprehensive upfront planning.
It's easy to see the time-box approach as a stop-gap measure, something you do "to get the project back on track." They might be uncomfortable with the approach because it can lead to micro-management, but I don't think that's a reason to give up on timeboxing. Instead, PM's would be well-suited to accept regular time-boxing as a way of life and then develop skills that help them avoid micro-management or other self-defeating behaviors.</description>
		<content:encoded><![CDATA[<p>I think some project managers think the one-week timebox approach is too much work. It is definitely a high-energy approach that requires the ability to re-focus at will, but I don&#8217;t think the overhead is as high as many people believe. It&#8217;s certainly less effort than plan management based on comprehensive upfront planning.<br />
It&#8217;s easy to see the time-box approach as a stop-gap measure, something you do &#8220;to get the project back on track.&#8221; They might be uncomfortable with the approach because it can lead to micro-management, but I don&#8217;t think that&#8217;s a reason to give up on timeboxing. Instead, PM&#8217;s would be well-suited to accept regular time-boxing as a way of life and then develop skills that help them avoid micro-management or other self-defeating behaviors.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
