<?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: Insomniapost</title>
	<atom:link href="http://nebunele.com/blog/2007/07/30/insomniapost/feed/" rel="self" type="application/rss+xml" />
	<link>http://nebunele.com/blog/2007/07/30/insomniapost/</link>
	<description>News about me that is of little interest to anyone except friends, family, and the occasional stalker</description>
	<lastBuildDate>Thu, 09 Sep 2010 14:19:16 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob</title>
		<link>http://nebunele.com/blog/2007/07/30/insomniapost/comment-page-1/#comment-675</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 02 Aug 2007 16:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://nebunele.com/blog/2007/07/30/insomniapost/#comment-675</guid>
		<description>The agile philosophy of software delivery has an interesting solution to this, here&#039;s a modified version:

Split your week into one day of planning and six of delivery.

Assume that the planning day will be chaotic and full of change as you adjust to all of the new factors that have arrived in the last week.

Lock in the six days to deliver just what you&#039;ve planned on in your planning day, or less.

On your planning day, create a detailed list of things that you will be able to accomplish in the next six days, like completely finish.  These could be sub-tasks.  Be realistic, don&#039;t push, be sane.  Prioritize your list.

Create a &#039;demo&#039; goal for your week&#039;s work and schedule time to show people who are important to you.  Make sure they know what you&#039;re going to be showing.

During the week, track how you&#039;re doing.  If you&#039;re behind, remove items from the bottom of the list.

At the end of the week, get up in front of your group and give a &#039;demo&#039; - show off what you&#039;ve accomplished.

On your next planning day, take into account what got done and adjust your expectations, also adjust your plan, you may end up doing something very different.

There&#039;s a lot more to it, but it&#039;s a great way of creating a realistic schedule and stabilizing a project.  The short window (usually 30 days in software) lets you realistically plan, the demo puts pressure on you, the 1 day chaos, 6 days heads-down helps keep things from spinning off into the ether.

The goal for the planning day is to have specific, bite-sized, actionable items.  &quot;Get everything for the new set.&quot; is too big, &quot;Pick out backdrop.&quot; &quot;Call 5 backdrop companies and get quotes.&quot; &quot;Order backdrop.&quot; are all good items.  Then when you&#039;re feeling anxiety, just pop three off the top and finish them.

If you wanted to add another layer to this, when you make your plan, predict the number of 15-minute segments each task will take and write it next to the task, then keep a little chart of the total amount of work left in the week and update it every night. (Update the estimates each night too if they&#039;ve changed.)

Another thought - if you finish the week&#039;s work early reward yourself with time off until the next planning day and then schedule more aggressively next time.  I find that if I have a reward for good productivity (aside from more work) I work better and more cleverly...

Just some thoughts.</description>
		<content:encoded><![CDATA[<p>The agile philosophy of software delivery has an interesting solution to this, here&#8217;s a modified version:</p>
<p>Split your week into one day of planning and six of delivery.</p>
<p>Assume that the planning day will be chaotic and full of change as you adjust to all of the new factors that have arrived in the last week.</p>
<p>Lock in the six days to deliver just what you&#8217;ve planned on in your planning day, or less.</p>
<p>On your planning day, create a detailed list of things that you will be able to accomplish in the next six days, like completely finish.  These could be sub-tasks.  Be realistic, don&#8217;t push, be sane.  Prioritize your list.</p>
<p>Create a &#8216;demo&#8217; goal for your week&#8217;s work and schedule time to show people who are important to you.  Make sure they know what you&#8217;re going to be showing.</p>
<p>During the week, track how you&#8217;re doing.  If you&#8217;re behind, remove items from the bottom of the list.</p>
<p>At the end of the week, get up in front of your group and give a &#8216;demo&#8217; &#8211; show off what you&#8217;ve accomplished.</p>
<p>On your next planning day, take into account what got done and adjust your expectations, also adjust your plan, you may end up doing something very different.</p>
<p>There&#8217;s a lot more to it, but it&#8217;s a great way of creating a realistic schedule and stabilizing a project.  The short window (usually 30 days in software) lets you realistically plan, the demo puts pressure on you, the 1 day chaos, 6 days heads-down helps keep things from spinning off into the ether.</p>
<p>The goal for the planning day is to have specific, bite-sized, actionable items.  &#8220;Get everything for the new set.&#8221; is too big, &#8220;Pick out backdrop.&#8221; &#8220;Call 5 backdrop companies and get quotes.&#8221; &#8220;Order backdrop.&#8221; are all good items.  Then when you&#8217;re feeling anxiety, just pop three off the top and finish them.</p>
<p>If you wanted to add another layer to this, when you make your plan, predict the number of 15-minute segments each task will take and write it next to the task, then keep a little chart of the total amount of work left in the week and update it every night. (Update the estimates each night too if they&#8217;ve changed.)</p>
<p>Another thought &#8211; if you finish the week&#8217;s work early reward yourself with time off until the next planning day and then schedule more aggressively next time.  I find that if I have a reward for good productivity (aside from more work) I work better and more cleverly&#8230;</p>
<p>Just some thoughts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
