<?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: 5 Practices for Managing (Constrained) Projects Successfully</title>
	<link>http://www.reformingprojectmanagement.com/2003/04/17/146/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sat, 30 Aug 2008 05:21:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Claude Emond
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/17/146/#comment-340</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/17/146/#comment-340</guid>
					<description>
        Nice wrap up from all three of you. Joe's first 3 out of 4 conclusions could be summed up as: 'SCRUM meets TOC'. 

I remember reading not to long ago an entry from Frank in te New Grange Forum asking WHY TOC-Critical Chain Project Management did not seem to be considered as part of Agile-Lean approaches in the eyes of certain others participants in the forum. I think, from what I read from you three, that the right question is not WHY but rather HOW they can be linked together. Joe gave the answer twice already : 'TOC tells you where, Lean (Agile) tells you how'(I added Agile as being family to Lean). 

And I guess it is the same answer for many approaches, be it the use of detailed WBS (alluded to by Hal in his list of recommendations) or other 'traditional-coined' approaches. (in the WBS case, Joe's statement could be :'WBS tells you what, Lean (Agile) tells you how'). 

Maybe if people were asking the right questions, like you did, before giving answers, it would be a lot easier to have real converging conversations, to build bridges between paradigms and come up with very useful things as you three just did. 

After all, Douglas Adam's answer to 'Life, the Universe and Everything' was 42 !!! But nobody really knows the exact wording of the question ! ;-)

I enjoyed every bit of it. 

Three personal Cheers for each of you (that makes 9 of them) 

Claude
      </description>
		<content:encoded><![CDATA[<p>Nice wrap up from all three of you. Joe&#8217;s first 3 out of 4 conclusions could be summed up as: &#8216;SCRUM meets <acronym title="Theory of Constraints; Eli Goldratt's insight on throughput">TOC</acronym>&#8217;. </p>
<p>I remember reading not to long ago an entry from Frank in te New Grange Forum asking WHY <acronym title="Theory of Constraints; Eli Goldratt's insight on throughput">TOC</acronym>-Critical Chain Project Management did not seem to be considered as part of Agile-Lean approaches in the eyes of certain others participants in the forum. I think, from what I read from you three, that the right question is not WHY but rather HOW they can be linked together. Joe gave the answer twice already : &#8216;<acronym title="Theory of Constraints; Eli Goldratt's insight on throughput">TOC</acronym> tells you where, Lean (Agile) tells you how&#8217;(I added Agile as being family to Lean). </p>
<p>And I guess it is the same answer for many approaches, be it the use of detailed <acronym title="Work Breakdown Structure; a way of bringing organization to the description and categories of work in a project">WBS</acronym> (alluded to by Hal in his list of recommendations) or other &#8216;traditional-coined&#8217; approaches. (in the <acronym title="Work Breakdown Structure; a way of bringing organization to the description and categories of work in a project">WBS</acronym> case, Joe&#8217;s statement could be :&#8217;<acronym title="Work Breakdown Structure; a way of bringing organization to the description and categories of work in a project">WBS</acronym> tells you what, Lean (Agile) tells you how&#8217;). </p>
<p>Maybe if people were asking the right questions, like you did, before giving answers, it would be a lot easier to have real converging conversations, to build bridges between paradigms and come up with very useful things as you three just did. </p>
<p>After all, Douglas Adam&#8217;s answer to &#8216;Life, the Universe and Everything&#8217; was 42 !!! But nobody really knows the exact wording of the question ! <img src='http://www.reformingprojectmanagement.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>I enjoyed every bit of it. </p>
<p>Three personal Cheers for each of you (that makes 9 of them) </p>
<p>Claude
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/17/146/#comment-341</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/17/146/#comment-341</guid>
					<description>
        Claude,

Thanks for you encouragement.  We had fun doing it.
      </description>
		<content:encoded><![CDATA[<p>Claude,</p>
<p>Thanks for you encouragement.  We had fun doing it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bolivar Senior
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/17/146/#comment-342</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/17/146/#comment-342</guid>
					<description>
        Hal:

Generally I am a batch reader of your blog. I allow a week or so to accumulate and then have my fix. Furthermore, I rarely visit your website, since I read your postings as email messages in my Palm. All this is the fanfare to say that the TOC series has been outstanding, especially combined with Joe and Frank blogs. I propose that you combine and preserve the series. Don’t let the entries die in a blog archive; it would be near-criminal.

I have my own strong opinions about TOC, generally positive, and about Critical Chain (CCM), generally negative. The problem with TOC is that it is frequently treated as a cult by its “followers,” who insist that salvation can only be granted to those that “believe” wholesale in Goldratt (sorry, today being Good Friday I feel mystical). I noticed that none of you addressed CCM in detail. Good for you. While CCM is good at discussing some CPM limitations, it offers poor alternatives to them (In fact, you may remember that I wrote a full-fledged discussion of CCM for Neenan back when you were their CEO). What if you take a respite, and discuss CCM at some point?

Regards,

Bolivar
      </description>
		<content:encoded><![CDATA[<p>Hal:</p>
<p>Generally I am a batch reader of your blog. I allow a week or so to accumulate and then have my fix. Furthermore, I rarely visit your website, since I read your postings as email messages in my Palm. All this is the fanfare to say that the <acronym title="Theory of Constraints; Eli Goldratt's insight on throughput">TOC</acronym> series has been outstanding, especially combined with Joe and Frank blogs. I propose that you combine and preserve the series. Don’t let the entries die in a blog archive; it would be near-criminal.</p>
<p>I have my own strong opinions about <acronym title="Theory of Constraints; Eli Goldratt's insight on throughput">TOC</acronym>, generally positive, and about Critical Chain (CCM), generally negative. The problem with <acronym title="Theory of Constraints; Eli Goldratt's insight on throughput">TOC</acronym> is that it is frequently treated as a cult by its “followers,” who insist that salvation can only be granted to those that “believe” wholesale in Goldratt (sorry, today being Good Friday I feel mystical). I noticed that none of you addressed CCM in detail. Good for you. While CCM is good at discussing some <acronym title="Critical Path Method: determines shortest sequence of steps thru a schedule">CPM</acronym> limitations, it offers poor alternatives to them (In fact, you may remember that I wrote a full-fledged discussion of CCM for Neenan back when you were their CEO). What if you take a respite, and discuss CCM at some point?</p>
<p>Regards,</p>
<p>Bolivar
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
