Project Management - CIOInsight
Home arrow Project Management arrow Why Big IT Projects Fail
RECENT NEWS

CIO STRATEGY
The Perfect IT Book for the Business?

Parkinson needs a book that explains IT to the business. Got any suggestions?    
KNOW IT ALL
By Tony Kontzer
The Cloud Debate: Public Versus Private

What does the legal battle between Salesforce.com and Microsoft really mean for the future of cloud computing?


  Project Management


Why Big IT Projects Fail

By Jay Bahel


There is a high correlation between lack of execution and dissatisfied shareholders.

Rate This Article:
Add This Article To:

See also:

Poor Planning Plagues Projects

Five ERP Disasters

Why do large projects fail to deliver?

Project Leadership Associates’ survey of more than 200 CEOs, COOs and CIOs suggests there is a high correlation between lack of execution and dissatisfied shareholders. Large projects specifically fail to meet shareholder expectations because they lack many things, such as buy-in within the project members, project managers who are business owners, clarity of plans and disciplined meeting management. Ambiguity of roles and responsibilities, team member burnout, and change management and cultural issues also contribute to this shortfall.

Our experience with more than 75 large projects suggests that success is closely tied to five “Execution Planning” steps:

Start with the steering committee. If there aren’t two or three sponsoring executives who choose to own a critical initiative within the business, don’t even start the initiative. Successful steering committees are primarily responsible for naming the members of the core project team, approving plans and providing strategic guidance to the core project team.

Establish the core project team. Successful core project teams include no more than four to six individuals who are responsible for making 80 percent of project decisions; building “straw models” and soliciting input/buy-in from other stakeholders (on issues such as master project timelines); aligning their sub-team leads to the master project timeline; holding sub-teams’ leads accountable for execution of the master project timeline; and escalating and resolving key project issues that may impede progress.

Establish sub-teams. Successful sub-team leads are responsible for developing and executing detailed plans (on schedule, budget and scope) in line with the master project timeline; recommending technical approaches and documenting them as required; and raising issues to sub-team peers and/or the core project team as necessary.

Define roles and responsibilities. Build a one-page graphical document that clearly defines objectives for all project members (in particular the core project team and sub-team leads). Successful large projects have core project teams that remove ambiguity of roles and responsibilities for both the sub-team leads and the core project team itself.

Build a one-page master project timeline. Successful core project teams publish a one-page graphical representation of the timeline for the project as a whole. These master project timelines have key “anchor dates” against which all sub-team leads are responsible for developing and executing detailed plans. This thinking differs from classical IT planning approaches.

Traditional project approaches start from the bottom up, with work-breakdown structures and task-level detail that roll into a detailed master project timeline. Our experience suggests that successful large projects start with key top-down anchor dates set forth from the core project team.

Effective IT strategy execution using these five steps overcomes the large project issues referenced earlier.

My future columns will cover other IT strategy execution tools and techniques. Continue to ask yourself, “How can these tools help me make a positive difference in my organization?”

Successful execution can make you invaluable in these tough economic times. These steps will help move your career forward.





Discuss Why Big IT Projects Fail
 
All the points in this article are valid, but there's a big one missing --...
Why do big IT projects fail? Let's not forget complexity. Often big projects are...
I came across the tirm, 'straw model' in this article for the first time. I seem to...
The idea of starting with the project planning with a high-level timelines seems...
Those are all great, if only looking strictly at management/execution. But if...
>>> Post your comment now!
 

 
 
>>> More Project Management Articles          >>> More By Jay Bahel
 


 
FEATURED SPONSORED MESSAGE

    A Center of Greener IT–and Savings

    Check out how IBM's Green Solutions Center is showcasing a number of IT solutions that are helping customers save significant costs when it comes to energy consumption.


FEATURED SPONSORED MESSAGE

    IT Locator

    Your next customer is searching for you. Will you be found? Get listed where customers search for IT experts.

EDITORS' PICKS
 
LATEST STORIES



FEEDBACK
Ziff Davis Enterprise RSS Feeds

Sponsored Links
  • Free 30-day endpoint security trial: VIPRE Enterprise
  • Download eval guide and prepare your apps for multicore.
  • Saugatuck Technology Research: CXO Top Priorities
  • Get expert tips & advice on IBM-Oracle database solutions.
  • Get Control with SonicWALL Application Intelligence
  • Free Trial: All-inclusive Enterprise Phone System
  • Reduce operating expenses with CDW Healthcare solutions.
  • FREE Data Leakage for Dummies Book from Sophos
  • eWEEK Quick LInks