<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.3" -->
<rss version="2.0">
	<channel>
		<title>Throw Out Complex Project Timelines!</title>
		<description>Comments for Throw Out Complex Project Timelines! at http://www.projecttimes.com , comment 1 to 5 out of 5 comments</description>
		<link>http://www.projecttimes.com</link>
		<lastBuildDate>Thu, 09 Sep 2010 08:08:01 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.3</generator>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/lisa-anderson/throw-out-complex-project-timelines.html#comment-290</link>
			<description>You hit the nail on the head.  I once had a PM that had such complicated timelines that it had to continually be revised because no one knew where they were in the process and therefore could not meet their milestones. Keeping it simple so all levels of the organization can understand the process is key. Thank you for your insight. - jill</description>
			<pubDate>Mon, 14 Sep 2009 08:21:59 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/lisa-anderson/throw-out-complex-project-timelines.html#comment-289</link>
			<description>Thank you for a clear and concise article on keeping the &quot;project&quot; clear and concise.  How often have I heard that a project has become mired in schedules that are consumed with too much detail or too many exceptions? - wkm</description>
			<pubDate>Sun, 13 Sep 2009 15:51:01 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/lisa-anderson/throw-out-complex-project-timelines.html#comment-288</link>
			<description>Absolutely - I couldn't agree more that people and team are #1 in determining project success.  Thanks for your comments and experiences. - Lisa Anderson</description>
			<pubDate>Wed, 09 Sep 2009 16:26:33 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/lisa-anderson/throw-out-complex-project-timelines.html#comment-286</link>
			<description>Any time a project manager is spending more time with the schedule than the team, there's a problem.  The schedule should be &quot;barely sufficient&quot; (to use an agile term), because it means nothing unless the team is performing.   - lmherrick</description>
			<pubDate>Wed, 09 Sep 2009 12:03:41 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/lisa-anderson/throw-out-complex-project-timelines.html#comment-284</link>
			<description>Exactly!  I'm working in the same dept with (against?) another PMP who is drowning his team in charts, timelines, fine details, forms, new tracking software and admits to not knowing the project status at any given time.  My team has delivered 4 projects over the past year (other PMP - none). Our team meets regularly, I produce status reports &amp; meet with the Executives to remove roadblocks and get decisions made, the team focuses on their assignments and due dates and we work with a very high level project plan that is understandable to all. Appreciation is necessary - I've reserved some budget $ for a small celebration at the end of our project. Yes, less is more!  Keep it simple and focused.  Good article.  DM - donna99</description>
			<pubDate>Wed, 09 Sep 2009 09:35:35 +0100</pubDate>
		</item>
	</channel>
</rss>
