<?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: How to Build a Project Schedule in 5 Easy Steps</title>
	<atom:link href="http://www.pmhut.com/how-to-build-a-project-schedule-in-5-easy-steps/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/how-to-build-a-project-schedule-in-5-easy-steps</link>
	<description></description>
	<pubDate>Sun, 12 Feb 2012 01:19:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mai</title>
		<link>http://www.pmhut.com/how-to-build-a-project-schedule-in-5-easy-steps/comment-page-1#comment-7056</link>
		<dc:creator>mai</dc:creator>
		<pubDate>Wed, 15 Jul 2009 01:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3171#comment-7056</guid>
		<description>topics are well presented and are easy to understand specially for beginners,good work, it came in handy for me</description>
		<content:encoded><![CDATA[<p>topics are well presented and are easy to understand specially for beginners,good work, it came in handy for me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gintas</title>
		<link>http://www.pmhut.com/how-to-build-a-project-schedule-in-5-easy-steps/comment-page-1#comment-2009</link>
		<dc:creator>Gintas</dc:creator>
		<pubDate>Fri, 22 May 2009 07:33:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3171#comment-2009</guid>
		<description>One important thing to remember here is that contingency reserves for cost and schedule must be added. It means that some risk management must be done perhaps on a high level at this point.</description>
		<content:encoded><![CDATA[<p>One important thing to remember here is that contingency reserves for cost and schedule must be added. It means that some risk management must be done perhaps on a high level at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Primoz Frelih</title>
		<link>http://www.pmhut.com/how-to-build-a-project-schedule-in-5-easy-steps/comment-page-1#comment-1986</link>
		<dc:creator>Primoz Frelih</dc:creator>
		<pubDate>Thu, 21 May 2009 19:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3171#comment-1986</guid>
		<description>Great post. This is one of the PMBOK topics, that could be grasped by a total beginner - a nice intro to project management.</description>
		<content:encoded><![CDATA[<p>Great post. This is one of the PMBOK topics, that could be grasped by a total beginner - a nice intro to project management.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elyse</title>
		<link>http://www.pmhut.com/how-to-build-a-project-schedule-in-5-easy-steps/comment-page-1#comment-1971</link>
		<dc:creator>Elyse</dc:creator>
		<pubDate>Thu, 21 May 2009 13:08:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3171#comment-1971</guid>
		<description>Great post for those new to our field.  Another suggestion is to do activities 1, 2, and 3 in a team setting.  Often I distribute the WBS before hand and schedule a workshop with the team.  One starts with just having the lifecycle on the table - Analyze, Design, Construction, Testing, Pre-Deployment, Deployment, Production Support.  The next step is to let the team members fill in thestart with the activity needed and time estimate.  After all the post its are inplace, sequence the work.  This activity really helps out with schedule construction, team building, shared understanding, and agreement to the schedule.  Does anyone help have any tips to share?

I hope this helps, and would welcome hearing suggestions from others,
Elyse</description>
		<content:encoded><![CDATA[<p>Great post for those new to our field.  Another suggestion is to do activities 1, 2, and 3 in a team setting.  Often I distribute the WBS before hand and schedule a workshop with the team.  One starts with just having the lifecycle on the table - Analyze, Design, Construction, Testing, Pre-Deployment, Deployment, Production Support.  The next step is to let the team members fill in thestart with the activity needed and time estimate.  After all the post its are inplace, sequence the work.  This activity really helps out with schedule construction, team building, shared understanding, and agreement to the schedule.  Does anyone help have any tips to share?</p>
<p>I hope this helps, and would welcome hearing suggestions from others,<br />
Elyse</p>
]]></content:encoded>
	</item>
</channel>
</rss>

