<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
         xmlns:thr="http://purl.org/syndication/thread/1.0" 
         xmlns:wfw="http://wellformedweb.org/CommentAPI/">
  <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2003/08/19/unfolding_projects.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2003/08/19/unfolding_projects.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2003://1.638-</id> 
  <updated>2007-12-03T12:12:55Z</updated>
  <title>Comments for Unfolding projects</title> 
  <subtitle>Jack Vinson writes about knowledge management, personal effectiveness, theory of constraints and more.  As of December 2007 Jack will likely start writing about product management too.</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.01</generator>

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2003://1.638" type="text/html" href="http://blog.jackvinson.com/archives/2003/08/19/unfolding_projects.html"/>


    <id>tag:blog.jackvinson.com,2003://1.638.288</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2003/08/19/unfolding_projects.html#comment-288" /> 
    <title>Comment from Hal on 2003-08-22</title>
    <author>
        <name>Hal</name> 
        <uri>http://weblog.halmacomber.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://weblog.halmacomber.com/">     
      <![CDATA[ <p>Hey Jack,</p>

<p>One of the challenges we face with an unfolding approach is with the formal systems of our company.  It can be a real pain in some companies to set up the accounting for a project once, let alone keep it up-to-date.  Customer contracts also constrain us.  We give in to the boilerplate language that requires us to operate to and report against a baseline schedule.  Yet, we have no choice but to stray from the plan as the project proceeds.</p>

<p>There are three things I encourage people to do:</p>

<p>1..set your plans at the highest possible level.<br />
2..add detail to the plan at the last responsible moment to take advantage of what you encounter and what you learn<br />
3..always plan with the people who are performing the work</p>

<p>These three steps support the emergence of a project and they still allow for the usual requirements to interact with the accounting systems and client contracts.</p>

<p>Thanks for reading Reforming Project Management!</p> ]]>
    </content>
    <published>2003-08-22T14:18:49Z</published>
    <updated>2003-08-22T14:18:49Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2003://1.638" type="text/html" href="http://blog.jackvinson.com/archives/2003/08/19/unfolding_projects.html"/>


    <id>tag:blog.jackvinson.com,2003://1.638.289</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2003/08/19/unfolding_projects.html#comment-289" /> 
    <title>Comment from Jack Vinson on 2003-08-22</title>
    <author>
        <name>Jack Vinson</name> 
        <uri>http://www.jackvinson.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.jackvinson.com">     
      <![CDATA[ <p>This is one of the areas where we have had the most difficulty in our critical chain implementation: balancing initial detail with the level of understanding available.  </p>

<p>From a technical standpoint, there has to be an easy way to define projects at the high level and then dive down into the details, once they are available - typically as you get near execution.  Of course, given the details, you may discover an unanticipated impact on the overall project.  But that is the price of uncertainty.</p> ]]>
    </content>
    <published>2003-08-22T16:47:03Z</published>
    <updated>2003-08-22T16:47:03Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2003://1.638" type="text/html" href="http://blog.jackvinson.com/archives/2003/08/19/unfolding_projects.html"/>


    <id>tag:blog.jackvinson.com,2003://1.638.290</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2003/08/19/unfolding_projects.html#comment-290" /> 
    <title>Comment from David C. Buchan on 2003-08-25</title>
    <author>
        <name>David C. Buchan</name> 
        <uri>http://www.thoughthorizon.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.thoughthorizon.com">     
      <![CDATA[ <p>This sounds quite like the approach taken by eXtreme Programming in that it gives the project permission to change from what was originally requested.  Typically and relentlessly software development projects are faced with changing customer priorities.  As these unfold into view, there are two options to choose from.  1) Stick to the original brief no matter what or 2) Adapt to the new priorities.  The latter means you will create something not previously planned for.  But the results count.  You have something you can use rather than a project plan which is worthless.</p> ]]>
    </content>
    <published>2003-08-25T23:40:41Z</published>
    <updated>2003-08-25T23:40:41Z</updated>

  </entry> 

</feed>
