<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Notes on Obsolete Theory</title>
	<link>http://www.reformingprojectmanagement.com/2003/03/13/130/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sat, 17 May 2008 07:03:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Claude Emond</title>
		<link>http://www.reformingprojectmanagement.com/2003/03/13/130/#comment-477</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/03/13/130/#comment-477</guid>
					<description>        Hello Hal,

you come back quite in good shape from your 3 day construction summit, and more resolved than ever to get get the 'reforms' coming to more and more people. 

Your notes on the Koskela and Howell paper were quite entertaining. I remember that in our first 'conversation' a couple of months ago, you told me about this paper and reading it was quite an experience for me. But, in retrospect (after fooling around with complexity theory, CAS and the like), I now find the paper a bit academic and leaving something unsaid, like a few down-to-earth solutions or advices to the common folks. Because of that, I don't feel it is good material to close a sale either. 
With respect to that, I would like to discuss the PMI issue that you mentioned, since I am quite active in this community. When I raised the question of obsolescence of the PMBoK model with fellow PMPs (making their living by spreading the PMBok model to already confused crowds), I was looked upon as an heretic. The fact that I was talking such nonsense while being the editor of the PMI Montreal Chapter newsletter also worried quite a few of my fellow 'deterministic managers'.
But, really, the question is not whether PMI is right or wrong. The issue is not PMI (the commercial entity), the issue is better project management in a complex world. And as you say, there are many people on official committees on the future (or the real present...) of project management, within the PMI, who also discuss the necessary shift from management-as-determining (or as-predicting)to management-as-adapting.
It is very important that, for people like me who keep and want to keep their association with PMI, while trying to reform project management, it is done by focussing on the needs and current ordeals of the real people that form PMI membership (it's only 100,000 people, but it is still quite a few persons on your back if you start questioning everything they do), not by focussing on the PMI current branding (which is irrelevant anyway to the every day problems that managers face). 
I have started to address the issue of management-as-adapting around me, not by talking obsolescence anymore, but by talking about our complex world, the reality of constant change and the possible virtues of self-adapting-organizing project teams, as demonstrated in agile SW development processes...in brief by offering possible solutions to every 'not-controlling-anything-anymore manager'. This way, I see less worried-angried eyes and more amused-playful smiles. I guess that for them, visualizing their project teams or organizations as self-organizing flights of Canadian geese or school of multicolor tropical fishes evolving happily in full harmony is a better prospect than feeling obsolete with nowhere to go. 
I guess I started to use my own professed medicine on me, management-as-adapting, in reaction to negative changes around me caused by an adversarial approach at reforming my fellow project managers and their organization. I started to walk the talk and it makes quite a difference not only in advocating a new approach but in living it and starting to see it in action. Just a small cautionary tale that I hope makes some sense and will be of some use. Salut !
      </description>
		<content:encoded><![CDATA[<p>Hello Hal,</p>
<p>you come back quite in good shape from your 3 day construction summit, and more resolved than ever to get get the &#8216;reforms&#8217; coming to more and more people. </p>
<p>Your notes on the Koskela and Howell paper were quite entertaining. I remember that in our first &#8216;conversation&#8217; a couple of months ago, you told me about this paper and reading it was quite an experience for me. But, in retrospect (after fooling around with complexity theory, CAS and the like), I now find the paper a bit academic and leaving something unsaid, like a few down-to-earth solutions or advices to the common folks. Because of that, I don&#8217;t feel it is good material to close a sale either.<br />
With respect to that, I would like to discuss the <acronym title="Project Management Institute">PMI</acronym> issue that you mentioned, since I am quite active in this community. When I raised the question of obsolescence of the <acronym title="PMI's Project Management Body of Knowledge">PMBoK</acronym> model with fellow PMPs (making their living by spreading the <acronym title="PMI's Project Management Body of Knowledge">PMBoK</acronym> model to already confused crowds), I was looked upon as an heretic. The fact that I was talking such nonsense while being the editor of the <acronym title="Project Management Institute">PMI</acronym> Montreal Chapter newsletter also worried quite a few of my fellow &#8216;deterministic managers&#8217;.<br />
But, really, the question is not whether <acronym title="Project Management Institute">PMI</acronym> is right or wrong. The issue is not <acronym title="Project Management Institute">PMI</acronym> (the commercial entity), the issue is better project management in a complex world. And as you say, there are many people on official committees on the future (or the real present&#8230;) of project management, within the <acronym title="Project Management Institute">PMI</acronym>, who also discuss the necessary shift from management-as-determining (or as-predicting)to management-as-adapting.<br />
It is very important that, for people like me who keep and want to keep their association with <acronym title="Project Management Institute">PMI</acronym>, while trying to reform project management, it is done by focussing on the needs and current ordeals of the real people that form <acronym title="Project Management Institute">PMI</acronym> membership (it&#8217;s only 100,000 people, but it is still quite a few persons on your back if you start questioning everything they do), not by focussing on the <acronym title="Project Management Institute">PMI</acronym> current branding (which is irrelevant anyway to the every day problems that managers face).<br />
I have started to address the issue of management-as-adapting around me, not by talking obsolescence anymore, but by talking about our complex world, the reality of constant change and the possible virtues of self-adapting-organizing project teams, as demonstrated in agile SW development processes&#8230;in brief by offering possible solutions to every &#8216;not-controlling-anything-anymore manager&#8217;. This way, I see less worried-angried eyes and more amused-playful smiles. I guess that for them, visualizing their project teams or organizations as self-organizing flights of Canadian geese or school of multicolor tropical fishes evolving happily in full harmony is a better prospect than feeling obsolete with nowhere to go.<br />
I guess I started to use my own professed medicine on me, management-as-adapting, in reaction to negative changes around me caused by an adversarial approach at reforming my fellow project managers and their organization. I started to walk the talk and it makes quite a difference not only in advocating a new approach but in living it and starting to see it in action. Just a small cautionary tale that I hope makes some sense and will be of some use. Salut !
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mary Poppendieck
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/03/13/130/#comment-478</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/03/13/130/#comment-478</guid>
					<description>
        It isn’t particularly useful to say that something is obsolete without offering an alternative.  I like to discuss concurrent engineering, widely adopted for product development in the 1990’s in response to work by Kim Clark, who studied the automotive product development process around the world in the late 1980’s. His astounding discovery was that product development practices which started early and committed late were 1/3 or more faster at developing new product, used half as many people, took half the time, and were on time three times as often!

The alternative to reductionist approaches such as WBS is aggregation.  Take a funnel (breadth first) approach to projects instead of a tunnel (depth first) approach.  Those of us in the north country understand ice sculpture contests.  Start with several big blocks of ice, do the big cuts and let the general shape emerge.  Refine gradually, increasing tolerances, first to the arms, legs, head, and so on, then to the detailing.  

If you think about sculpture instead of machines, then you can see how emergence works.  It beats flocking birds and ant colonies….

Mary
      </description>
		<content:encoded><![CDATA[<p>It isn’t particularly useful to say that something is obsolete without offering an alternative.  I like to discuss concurrent engineering, widely adopted for product development in the 1990’s in response to work by Kim Clark, who studied the automotive product development process around the world in the late 1980’s. His astounding discovery was that product development practices which started early and committed late were 1/3 or more faster at developing new product, used half as many people, took half the time, and were on time three times as often!</p>
<p>The alternative to reductionist approaches such as <acronym title="Work Breakdown Structure; a way of bringing organization to the description and categories of work in a project">WBS</acronym> is aggregation.  Take a funnel (breadth first) approach to projects instead of a tunnel (depth first) approach.  Those of us in the north country understand ice sculpture contests.  Start with several big blocks of ice, do the big cuts and let the general shape emerge.  Refine gradually, increasing tolerances, first to the arms, legs, head, and so on, then to the detailing.  </p>
<p>If you think about sculpture instead of machines, then you can see how emergence works.  It beats flocking birds and ant colonies….</p>
<p>Mary
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Claude Emond
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/03/13/130/#comment-479</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/03/13/130/#comment-479</guid>
					<description>
        Thank you very much for the ice sculpture analogy, Mary. I am going to use it on my less poetic and less gregarious friends with more success, I guess, that my natural analogies (flocks, flights, schools, colonies and the like). 

The funnel vs tunnel approach is something I use a lot while tackling project portfolio management issues; but the idea of using the funnel analogy for one project is new to me (usually after the portfolio selection funnel, my projects fall into a big pipeline-tunnel--I guess, as you propose I ought to keep a few single-project-size funnels to explain how to start them). Makes my day !
      </description>
		<content:encoded><![CDATA[<p>Thank you very much for the ice sculpture analogy, Mary. I am going to use it on my less poetic and less gregarious friends with more success, I guess, that my natural analogies (flocks, flights, schools, colonies and the like). </p>
<p>The funnel vs tunnel approach is something I use a lot while tackling project portfolio management issues; but the idea of using the funnel analogy for one project is new to me (usually after the portfolio selection funnel, my projects fall into a big pipeline-tunnel&#8211;I guess, as you propose I ought to keep a few single-project-size funnels to explain how to start them). Makes my day !
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Claude Emond
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/03/13/130/#comment-480</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/03/13/130/#comment-480</guid>
					<description>
        I also feel that the paper is quite useful.For a start, Koskela and Howell shook the hell out of a few of my beliefs which is far from being trivial. But now that my beliefs are on fire, I gotta find some water fast. I also believe that this water resides in the wonders of human messiness and that, while conversing, we are going to find the well...although for now I sometimes find that I am nothing but a hard thinking Canadian beaver. But I am happy not to be a colony of one.
      </description>
		<content:encoded><![CDATA[<p>I also feel that the paper is quite useful.For a start, Koskela and Howell shook the hell out of a few of my beliefs which is far from being trivial. But now that my beliefs are on fire, I gotta find some water fast. I also believe that this water resides in the wonders of human messiness and that, while conversing, we are going to find the well&#8230;although for now I sometimes find that I am nothing but a hard thinking Canadian beaver. But I am happy not to be a colony of one.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
