<?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 Management News &#187; Dr. Karen McGraw</title>
	<atom:link href="http://www.itmanagementnews.com/author/dr-karen-mcgraw/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.itmanagementnews.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 26 Jan 2012 17:18:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Improving Project Success Rates with Better Leadership</title>
		<link>http://www.itmanagementnews.com/2009/05/14/improving-project-success-rates-with-better-leadership/</link>
		<comments>http://www.itmanagementnews.com/2009/05/14/improving-project-success-rates-with-better-leadership/#comments</comments>
		<pubDate>Thu, 14 May 2009 13:25:39 +0000</pubDate>
		<dc:creator>Dr. Karen McGraw</dc:creator>
				<category><![CDATA[Discussions]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://www.itmanagementnews.com/?p=48</guid>
		<description><![CDATA[Introduction Factual and anecdotal evidence confirms that IT investments are inherently risky. On average, about 70% of all IT related projects fail to meet their on-time, on-budget objectives or to produce the expected business results. In one KPMG survey, 67% of the companies who participated said that their program/project management function was in need of [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Introduction</strong></p>
<p>Factual  and anecdotal evidence confirms that IT investments are inherently  risky.  On average, about 70% of all IT related projects fail to meet  their on-time, on-budget objectives or to produce the expected  business results.  In one KPMG survey, 67% of the companies who  participated said that their program/project management function was  in need of improvement.  Why?  A number of leading factors for  project failure were suggested by the survey, including the “usual  suspects”: unreasonable project timelines, poorly defined  requirements, poor scope management, and unclear project objectives.   Granted, all of these factors can play a role in project success.   But are they the cause or project failure, or just a symptom of some  larger issue?  In this article, we will discuss that the root cause  for many of these common failure points is really the ability to <em>lead</em> projects, not just manage them.</p>
<p><span id="more-48"></span><br />
<strong>Leadership: Missing in Action</strong></p>
<p>One  would think that the proliferation of certified PMPs would have  increased IT project success rates. However, given the research  previously cited, this does not appear to be the case.  Certainly,  PMPs are cognizant of the processes, techniques and tools that should  be used to manage projects and have documented project management  experience.  We contend that certification—the PMP—is indeed  important, but that it alone is not sufficient for successful project  management. Having been called on to rescue and turnaround numerous  IT projects, we have had the opportunity to analyze why a project  gets in trouble.  As we looked at several of these troubled projects  we realized that there appears to be a common link: leadership is  missing in action.  That is, while the project manager may be focused  on what needs to be done and may well know how to do it, he or she  may not be acting as a project <em>leader</em>.   While certification is a good foundation for knowing what to do, it  takes true leadership to drive complex projects to successful  conclusions. </p>
<p>The PMI <em>Body of Knowledge</em> specifies five process groups for project management:  Initiating,  Planning, Executing, Controlling and Monitoring, and Closing.  These  five areas are consistent with the functions of management within an  organization.  Managers are responsible for planning, organizing,  directing, resourcing, and controlling for the purpose of achieving  organizational goals.  The certified project manager should be able  to demonstrate competent management of the nine PMI knowledge areas:  project integration, scope, time, quality, cost, human resources,  communications, risks, and procurement. </p>
<p>However,  the ability to manage each of these project areas still may not  produce successful project outcomes.  Our experience on client sites  for both government and commercial clients reveals that project  leadership, not just management, is the critical differentiator.   Project <em>management</em> without project <em>leadership</em> is likely to result in project failure.</p>
<p>Certainly,  it is not our intent to redefine leadership.  It’s already been  defined <em>as t</em><SPAN LANG="en"><em>he  ability to affect human behavior to accomplish a mission or the act  of influencing a people to set and achieve goals</em></SPAN><SPAN LANG="en">. </SPAN>Volumes of business and strategy texts  have been written about this critical competency.  Check out your  local book store and you will see numerous titles identifying  leadership styles, leadership characteristics, and inspirational  leadership topics. Some authors or practitioners have made the point  that leadership and management represent two different skill sets and  that either an individual has the characteristics and skills  necessary for leadership <em>or</em> those more appropriate for management.  Others have suggested that  leadership is knowing where to go and that management is all about  how to actually get there.  We find this dichotomy troubling and  perhaps at the heart of our IT project management failure rate.   Instead, we believe that not only <em>can</em> project managers act as leaders, but in fact that they must provide  leadership if projects are to achieve results. </p>
<p><strong>A Closer Look at Project Leadership</strong></p>
<p>Project  leadership is all about shaping a team of diverse individuals  (employers and contractors, some from different organizations) into a  force that produces measureable project results.  At our company, we  recruit and develop project managers who can provide the leadership  that complex IT projects require.  At a basic level, project managers  must be able to set the vision, define success, and determine the  measurements of success.  Then they must inspire, persuade, and lead  the project team. </p>
<p>We  argue that for project managers to become project leaders, they must  demonstrate competence in three essential skill areas.  Successful  project leadership involves:</p>
<p><UL><br />
  <LI></p>
<p>Leading  	courageously </p>
<p>  <LI></p>
<p>Influencing  	others</p>
<p>  <LI></p>
<p>Acting  	with resilience</p>
<p></UL></p>
<p><strong>Leading  courageously</strong> is a critical competency because  large IT projects have a huge resource pool representing different  organizations and job roles.  These resources may see their tasks  slightly differently and may not all be aligned with project goals.   Furthermore, the sheer number of issues and risks may make it  difficult to zero in on those tasks that are most critical.  In this  kind of environment, leading courageously can easily make the  difference between success and failure.  Leading courageously means  clarifying what is important and taking a stand to resolve important  issues. It also requires driving hard on the right issues and  confronting problems promptly. Finally, courageous project leadership  means being decisive and challenging others to make tough choices. </p>
<p><strong>Influencing  others</strong> is an essential competency for most  projects, but especially for those with large project teams, numerous  stakeholders, and different user communities.<strong> </strong>Influencing others<strong> </strong>means giving compelling reasons for ideas and  suggestions and winning support from others, both within the project  team and in the user and stakeholder community.  It also requires the  ability to negotiate persuasively and get others to take action.  Finally, it means influencing the decisions of upper management,  whether within your own organization or the client organization.</p>
<p><strong>Acting  with resilience</strong> is critical to project  leadership and is especially important when projects are at critical  stages or in trouble.  When a project manager acts with resilience,  he or she keeps the focus on project goals and refuses to give up.  Sometimes it means being tough enough, in the face of adversity, to  fight the good fight and get agreement on issues that threaten to  derail the project.  Or it may simply require being flexible enough  to negotiate solutions that keep driving for the goal of project  success, when others might give up and accept defeat.</p>
<p><strong>Summing It Up</strong></p>
<p>In this  article we’ve presented the case that project leadership is the  differentiating factor in project success, especially on large,  mission-critical projects.  Knowing what to do and being able to  manage the nine knowledge areas identified by PMI is not enough on  complex projects. </p>
<p>Successful  project managers <em>must</em> lead courageously and be able to influence others to resolve some of  the most critical problems that projects experience.  And to  paraphrase Churchill, they must never, ever give up; they must act  with resilience even in the face of conflict and problems. To  experience the project success that investments demand, assign  project managers who can act as <em>project  leaders</em> to your mission-critical IT projects. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.itmanagementnews.com/2009/05/14/improving-project-success-rates-with-better-leadership/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

