<?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: Serial Monogamy Project Participation</title>
	<atom:link href="http://jrothman.com/blog/mpd/2009/01/serial-monogamy-project-participation.html/feed" rel="self" type="application/rss+xml" />
	<link>http://jrothman.com/blog/mpd/2009/01/serial-monogamy-project-participation.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>
	<lastBuildDate>Tue, 16 Mar 2010 19:31:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brendan</title>
		<link>http://jrothman.com/blog/mpd/2009/01/serial-monogamy-project-participation.html/comment-page-1#comment-32649</link>
		<dc:creator>Brendan</dc:creator>
		<pubDate>Mon, 19 Jan 2009 19:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8604#comment-32649</guid>
		<description>I think this approach is ideal when developing products. However, what if you have an established product that you are selling externally? Clients need some basic understanding of when features will be completed. If you are asking them for 6 and  7 figure dollars, simply saying we are working on only one project now may cause them to take their business elsewhere. What about revenue forecasting? If I am going to my CEO and saying that we can not earn such and such revenue because the team needs slack time, I will get fired. Do not get me wrong, I am a believer in slack time and its benefits, many unplanned activities come up regularly and teams should be empowered. But as a head of a PMO, this puts resource planning and revenue forecasting at odds with one another. We are actively managing this by developing adaptive release plans based on team capacities. This allows us to make loose commitments based on a ever changing plan (which we are ok with) and engage with clients on a fix time and cost basis.</description>
		<content:encoded><![CDATA[<p>I think this approach is ideal when developing products. However, what if you have an established product that you are selling externally? Clients need some basic understanding of when features will be completed. If you are asking them for 6 and  7 figure dollars, simply saying we are working on only one project now may cause them to take their business elsewhere. What about revenue forecasting? If I am going to my CEO and saying that we can not earn such and such revenue because the team needs slack time, I will get fired. Do not get me wrong, I am a believer in slack time and its benefits, many unplanned activities come up regularly and teams should be empowered. But as a head of a PMO, this puts resource planning and revenue forecasting at odds with one another. We are actively managing this by developing adaptive release plans based on team capacities. This allows us to make loose commitments based on a ever changing plan (which we are ok with) and engage with clients on a fix time and cost basis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Ward</title>
		<link>http://jrothman.com/blog/mpd/2009/01/serial-monogamy-project-participation.html/comment-page-1#comment-32400</link>
		<dc:creator>Jim Ward</dc:creator>
		<pubDate>Mon, 12 Jan 2009 17:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8604#comment-32400</guid>
		<description>When I teach project management, I use something called a &quot;Productivity Factor&quot; developed by the Keane consulting organization. Only a certain percentage of an individual&#039;s time is available for project work, whether they are dedicated to a single project (the ideal situation) or more that one project (not ideal). That factor in most organizations is significantly less that 80% in my experience, usually between 60-70%. So even if someone is assigned full time to a single project, we can expect that the person will devote 3 to 3 1/2 days per week of effort to that project. This is a realistic performance estimate, allows time for the other activities you suggest and avoids much of the schedule slippage and excessive overtime that plague many projects.</description>
		<content:encoded><![CDATA[<p>When I teach project management, I use something called a &#8220;Productivity Factor&#8221; developed by the Keane consulting organization. Only a certain percentage of an individual&#8217;s time is available for project work, whether they are dedicated to a single project (the ideal situation) or more that one project (not ideal). That factor in most organizations is significantly less that 80% in my experience, usually between 60-70%. So even if someone is assigned full time to a single project, we can expect that the person will devote 3 to 3 1/2 days per week of effort to that project. This is a realistic performance estimate, allows time for the other activities you suggest and avoids much of the schedule slippage and excessive overtime that plague many projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dwayne Phillips</title>
		<link>http://jrothman.com/blog/mpd/2009/01/serial-monogamy-project-participation.html/comment-page-1#comment-32391</link>
		<dc:creator>Dwayne Phillips</dc:creator>
		<pubDate>Mon, 12 Jan 2009 12:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8604#comment-32391</guid>
		<description>I like the twist on your theme. Slack or &quot;management reserve&quot; is important. I guess you are talking about &quot;personal reserve.&quot; The ability to surge into something else is important.</description>
		<content:encoded><![CDATA[<p>I like the twist on your theme. Slack or &#8220;management reserve&#8221; is important. I guess you are talking about &#8220;personal reserve.&#8221; The ability to surge into something else is important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheoRadical &#187; Blog Archive &#187; One Thing at a Time</title>
		<link>http://jrothman.com/blog/mpd/2009/01/serial-monogamy-project-participation.html/comment-page-1#comment-32373</link>
		<dc:creator>TheoRadical &#187; Blog Archive &#187; One Thing at a Time</dc:creator>
		<pubDate>Sun, 11 Jan 2009 17:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8604#comment-32373</guid>
		<description>[...] Over at MPD they&#8217;re talking about doing one project at a time. Recently, I have been doing this at work as well. I schedule out which things I am working on each day, and I try to keep it to one large task, or two smalls tasks. This gives enough padding to achieve the 80% &#8220;committed&#8221; the article talks about. If you&#8217;re spread all over hell going 100% all the time, the very next interruption will ruin everything. You&#8217;re next three projects will all be late and poor quality. [...]</description>
		<content:encoded><![CDATA[<p>[...] Over at MPD they&#8217;re talking about doing one project at a time. Recently, I have been doing this at work as well. I schedule out which things I am working on each day, and I try to keep it to one large task, or two smalls tasks. This gives enough padding to achieve the 80% &#8220;committed&#8221; the article talks about. If you&#8217;re spread all over hell going 100% all the time, the very next interruption will ruin everything. You&#8217;re next three projects will all be late and poor quality. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
