<?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: Meetings, Project Portfolio, and Lean</title>
	<atom:link href="http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html/feed" rel="self" type="application/rss+xml" />
	<link>http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.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>Sat, 22 Nov 2008 02:17:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Steve Holt</title>
		<link>http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html#comment-9378</link>
		<dc:creator>Steve Holt</dc:creator>
		<pubDate>Wed, 28 May 2008 18:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html#comment-9378</guid>
		<description>Regarding your search for a reference regarding quality and quantity of management decisions, I first saw this point made by Ajai Kapoor of Realization Technologies at the 2005 Theory of Constrains International Certification Organization annual conference. His point was that as projects are staggered it reduces the decision making multi-tasking of managers and, hence, people reporting to them spend less time waiting for answers and projects complete faster with higher quality. This, in turn, means fewer rework loops and fewer decisions for managers, leading to even faster projects. It creates a "virtuous circle" in which the  benefits reinforce each other. You can see references to the point in the Postscripts from Realization's past conferences here: http://www.realization.com/postscripts.htm

This has been pseudo-codified within the Critical Chain Project Management community by rules of thumb saying that in a massively multi-tasking project system 25% of all projects should immediately be frozen to provide sufficient time for people (and managers) to get to the tasks that are stacking up-including management decisions. (Some go further and say that first 25% of current projects should be outright canceled since they won't be completed anyway.)</description>
		<content:encoded><![CDATA[<p>Regarding your search for a reference regarding quality and quantity of management decisions, I first saw this point made by Ajai Kapoor of Realization Technologies at the 2005 Theory of Constrains International Certification Organization annual conference. His point was that as projects are staggered it reduces the decision making multi-tasking of managers and, hence, people reporting to them spend less time waiting for answers and projects complete faster with higher quality. This, in turn, means fewer rework loops and fewer decisions for managers, leading to even faster projects. It creates a &#8220;virtuous circle&#8221; in which the  benefits reinforce each other. You can see references to the point in the Postscripts from Realization&#8217;s past conferences here: <a href="http://www.realization.com/postscripts.htm" rel="nofollow">http://www.realization.com/postscripts.htm</a></p>
<p>This has been pseudo-codified within the Critical Chain Project Management community by rules of thumb saying that in a massively multi-tasking project system 25% of all projects should immediately be frozen to provide sufficient time for people (and managers) to get to the tasks that are stacking up-including management decisions. (Some go further and say that first 25% of current projects should be outright canceled since they won&#8217;t be completed anyway.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jim ward</title>
		<link>http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html#comment-9358</link>
		<dc:creator>jim ward</dc:creator>
		<pubDate>Wed, 28 May 2008 13:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html#comment-9358</guid>
		<description>I am a little confused by the above. I am assuming that you are talking about functional managers as opposed to project managers. I do not believe that managers should be making many decisions about projects. The decision about whether to authorize and staff a project belongs to management. The decision about who should manage the project is also a management decision. After those decisions are made, the project manager should have the authority to make virtually all project related decisions. Maybe I need some specific examples from you about project related decisions that managers are making on a weekly basis.</description>
		<content:encoded><![CDATA[<p>I am a little confused by the above. I am assuming that you are talking about functional managers as opposed to project managers. I do not believe that managers should be making many decisions about projects. The decision about whether to authorize and staff a project belongs to management. The decision about who should manage the project is also a management decision. After those decisions are made, the project manager should have the authority to make virtually all project related decisions. Maybe I need some specific examples from you about project related decisions that managers are making on a weekly basis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Arnold</title>
		<link>http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html#comment-9354</link>
		<dc:creator>Joe Arnold</dc:creator>
		<pubDate>Wed, 28 May 2008 12:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html#comment-9354</guid>
		<description>I love these tactical methods like these to highlight what is really happening. Useful tool. My previous indicators were merely how stressed-out or frantic they were.</description>
		<content:encoded><![CDATA[<p>I love these tactical methods like these to highlight what is really happening. Useful tool. My previous indicators were merely how stressed-out or frantic they were.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dwayne Phillips</title>
		<link>http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html#comment-9350</link>
		<dc:creator>Dwayne Phillips</dc:creator>
		<pubDate>Wed, 28 May 2008 11:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/2008/05/meetings-project-portfolio-and-lean.html#comment-9350</guid>
		<description>Interesting thoughts. I especially agree with the concept that few decisions are more obvious than many decisions, hence the insecure manager (the one striving to be perfect) would rather make many decisions as hiding poor decisions is easier. 

My current office has about twice as many projects as we should. The managers cannot seem to cancel any despite all the engineers begging them to. Fear is a tough devil at work.</description>
		<content:encoded><![CDATA[<p>Interesting thoughts. I especially agree with the concept that few decisions are more obvious than many decisions, hence the insecure manager (the one striving to be perfect) would rather make many decisions as hiding poor decisions is easier. </p>
<p>My current office has about twice as many projects as we should. The managers cannot seem to cancel any despite all the engineers begging them to. Fear is a tough devil at work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
