<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IT Project Mechanic &#187; PM</title>
	<atom:link href="http://itprojectmechanic.com/itpmlog/index.php/category/pm/feed/" rel="self" type="application/rss+xml" />
	<link>http://itprojectmechanic.com/itpmlog</link>
	<description>give your IT Projects a tune-up</description>
	<lastBuildDate>Mon, 29 Jun 2009 19:41:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How do you define problems your projects are designed to resolve?</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/06/10/how-do-you-define-problems-your-projects-are-designed-to-resolve/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/06/10/how-do-you-define-problems-your-projects-are-designed-to-resolve/#comments</comments>
		<pubDate>Tue, 10 Jun 2008 13:08:23 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[Conceptual]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Project Success]]></category>
		<category><![CDATA[Uncategorized]]></category>
<category>about</category><category>IT</category><category>problem</category><category>process</category><category>project</category><category>success</category><category>waste</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/index.php/2008/06/10/how-do-you-define-problems-your-projects-are-designed-to-resolve/</guid>
		<description><![CDATA[When most projects start out they have an identified problem that is driving the effort.  Every project I&#8217;ve been a part of, or can think of for that matter, has at it&#8217;s core a problem, perceived problem or need that is moving people to action.  I believe that a large number of these [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/06/10/how-do-you-define-problems-your-projects-are-designed-to-resolve/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Forget about the solution; what are the needs?</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/04/14/forget-about-the-solution-what-are-the-needs/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/04/14/forget-about-the-solution-what-are-the-needs/#comments</comments>
		<pubDate>Mon, 14 Apr 2008 14:17:23 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[Conceptual]]></category>
<category>approach</category><category>problem</category><category>project</category><category>truths</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/index.php/2008/04/14/forget-about-the-solution-what-are-the-needs/</guid>
		<description><![CDATA[I&#8217;ve been a proponent (much to the chagrin of some of my team mates) of the idea that organizations don&#8217;t understand the problems they&#8217;re trying to solve for quite some time.  This sounds absurd on the face of things &#8211; why would an organization sink time, money and resources into a solution for a [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/04/14/forget-about-the-solution-what-are-the-needs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Project Management &#8211; Focus on the Basics pt1 – Scope Management</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/04/01/pm_focusonthebasics_scope/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/04/01/pm_focusonthebasics_scope/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 18:40:38 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[Uncategorized]]></category>
<category>approach</category><category>basics</category><category>IT</category><category>managing</category><category>PM</category><category>project</category><category>stakeholders</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/index.php/2008/04/01/pm_focusonthebasics_scope/</guid>
		<description><![CDATA[Today begins the first in a series of entries about focusing on the basics of Project Management. With all of the “flavors” of Project Management these days (Scrum, Agile, traditional, waterfall, RUP, CMMI, etc) the basic tenets of any PM methodology are the same – help remove risk, ensure optimal performance and deliver the project [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/04/01/pm_focusonthebasics_scope/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Experience Verification support form for the PMP Application</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/04/01/experience-verification-support-form-for-the-pmp-application/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/04/01/experience-verification-support-form-for-the-pmp-application/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 16:47:12 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[PM]]></category>
<category>IT</category><category>PM</category><category>PMI</category><category>PMP</category><category>process</category><category>project</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/index.php/2008/04/01/experience-verification-support-form-for-the-pmp-application/</guid>
		<description><![CDATA[For many, the task of filling out the PMP certification application can be more daunting than the exam.  Fear not, however, for there is an easier way.
The most laborious task is Section III, the Experience Verification form.  Now, while this form is straightforward, it should help you save time and anixety when you [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/04/01/experience-verification-support-form-for-the-pmp-application/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blog posting on ITtoolbox</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/03/20/blog-posting-on-ittoolbox/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/03/20/blog-posting-on-ittoolbox/#comments</comments>
		<pubDate>Fri, 21 Mar 2008 04:54:11 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[IT Projects]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Requirements]]></category>
		<category><![CDATA[Results]]></category>
<category>Documentation</category><category>it</category><category>project</category><category>requirements</category><category>Results</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/index.php/2008/03/20/blog-posting-on-ittoolbox-itprojectmechanic/</guid>
		<description><![CDATA[I&#8217;m blogging at www.ittoolbox.com/pm/itprojectmechanic and thought you might want to review the article that I posted there called &#8220;Why am I doing this?&#8221;
You can visit the blog here: http://blogs.ittoolbox.com/pm/itprojectmechanic/archives/why-am-i-doing-this-23212
 A question that I sometimes ask myself (in frustration I might add) is something that ought to be written on the top of my monitor &#8211; [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/03/20/blog-posting-on-ittoolbox/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why is this happening?!?!?</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/03/12/why-is-this-happening/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/03/12/why-is-this-happening/#comments</comments>
		<pubDate>Wed, 12 Mar 2008 16:03:51 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[IT Projects]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Stakeholders]]></category>
		<category><![CDATA[Tune-Ups]]></category>
<category>IT</category><category>PM</category><category>problem</category><category>process</category><category>project</category><category>Results</category><category>stakeholders</category><category>success</category><category>troubled</category><category>WBS</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/index.php/2008/03/12/why-is-this-happening/</guid>
		<description><![CDATA[Every PM I have met along my journey has had at least one, if not a few, projects that could be modestly described as troubled.  In fact, I think this is a pretty standard occurrence in the Project Manager ranks &#8211; there are projects that despite our best efforts, quality training and experience, spend [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/03/12/why-is-this-happening/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interesting article on SearchCIO.com &#8211; CIO &amp; the PPM Strategy</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/03/10/30/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/03/10/30/#comments</comments>
		<pubDate>Mon, 10 Mar 2008 23:25:30 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Measurement]]></category>
		<category><![CDATA[PM_Software]]></category>
<category>ppm strategy tools</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/index.php/2008/03/10/30/</guid>
		<description><![CDATA[ I was surfing the blogosphere and ran across an article about how Project and Portfolio Management strategy (and software) are musts for CIOs in hard times &#8211; I would argue that the belt tightening in lean times and the wild-wild-west rules when times are good is all the more reason to invest in PPM [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/03/10/30/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple ways to find the problem (whatever it is)</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/03/06/simple-ways-to-find-the-problem-whatever-it-is/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/03/06/simple-ways-to-find-the-problem-whatever-it-is/#comments</comments>
		<pubDate>Thu, 06 Mar 2008 17:14:29 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[General Maintenance]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[Team]]></category>
<category>brainstorm</category><category>IT</category><category>PM</category><category>problem</category><category>process</category><category>project</category><category>simple</category><category>skills</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/index.php/2008/03/06/simple-ways-to-find-the-problem-whatever-it-is/</guid>
		<description><![CDATA[I would say that my job, as a project manager, constitutes a mix of the following: project chaperone, creative solution-maker and thorough problem surveyor.  There are other bits, but I was left on an island with a mega-bank as my client and only three things would be left out of my bag of tricks, [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/03/06/simple-ways-to-find-the-problem-whatever-it-is/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PM Software &#8211; GanttProject</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2008/02/29/pm-software-ganttproject/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2008/02/29/pm-software-ganttproject/#comments</comments>
		<pubDate>Fri, 29 Feb 2008 19:05:50 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[PM]]></category>
		<category><![CDATA[PM_Software]]></category>
		<category><![CDATA[ganttproject]]></category>
		<category><![CDATA[project]]></category>
		<category><![CDATA[Requirements]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[tool]]></category>
<category>ganttproject</category><category>PM</category><category>project</category><category>Requirements</category><category>software</category><category>tool</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/?p=25</guid>
		<description><![CDATA[In the series, Finding the right PM software package, I set about trying to find the few &#8217;shining stars&#8217; out of the hundreds of applications that I am aware of.  I&#8217;m not limiting this search to commercial, off the shelf software or to desktop applications &#8211; the sector is getting incredibly large and spans [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2008/02/29/pm-software-ganttproject/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Secrets of the documentation abyss</title>
		<link>http://itprojectmechanic.com/itpmlog/index.php/2007/08/10/secrets-of-the-documentation-abyss/</link>
		<comments>http://itprojectmechanic.com/itpmlog/index.php/2007/08/10/secrets-of-the-documentation-abyss/#comments</comments>
		<pubDate>Fri, 10 Aug 2007 16:03:00 +0000</pubDate>
		<dc:creator>CrisRogers</dc:creator>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[artifact]]></category>
		<category><![CDATA[deliverable]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[project]]></category>
		<category><![CDATA[waste]]></category>
<category>artifact</category><category>deliverable</category><category>Documentation</category><category>process</category><category>project</category><category>requirements</category><category>waste</category>
		<guid isPermaLink="false">http://itprojectmechanic.com/itpmlog/?p=23</guid>
		<description><![CDATA[Why are most documents created for projects never reviewed after approval?
Once upon a time, I was consulting for a company in Florida who was implementing controls in their systems.  The management was insistent that every step of the process be documented to the letter.  As the project manager, I began to carry these [...]]]></description>
		<wfw:commentRss>http://itprojectmechanic.com/itpmlog/index.php/2007/08/10/secrets-of-the-documentation-abyss/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
