IT management regularly encounters projects with problematic prospects that are not progressing as expected. It’s not a pretty sight.

A nagging feeling tells you that something is just not right. You definitely don’t want the failure of a project to damage your reputation, the reputation of your organization, or its carefully cultivated brand. Nor do you want others in the organization to view your project as a boondoggle or a career-killing project.

Here is a list of the top 11 reasons for failure, with questions that may help you save projects. Acting on the answers will help you recover a project from crashing and burning.

1. Insufficient planning

The project is failing because the planning process was shortened due to time pressure. Ask these questions to adequately address the planning process:

  1. Is the project charter sufficiently complete to form the basis for planning the project?
  2. Is the project management plan sufficiently detailed to form the basis for a rational implementation of the project?
  3. Is there a reasonably complete risk register?

2. Inadequate leadership

The project is failing because of inadequate leadership. Ask these questions to deal adequately with leadership:

  1. Is the project sponsor engaged?
  2. Does the project manager have enough experience, given the characteristics of the project?
  3. Have either of the individuals in these roles ended up in their roles more by chance rather than by conscious selection?

3. Unclear goals and objectives

The project is failing due to unclear goals and objectives. Ask these questions to adequately address goals and objectives:

  1. How measurable are the goals and objectives?
  2. How realistic are the goals and objectives given constraints of skills, experience and budget?
  3. Do goals and objectives focus on business value and not on technical details?

Use the SMART framework with your team to clarify goals and objectives.

4. Lack of resource planning

The project is failing because the planning process did not pay enough attention to resource management. Ask these questions to adequately address resource management:

  1. Which team members (with what technical and non-technical skills and experience) are required? Do we have them?
  2. What knowledge resources do we lack? Can we hire experts or provide training to build the skills required for my team?
  3. About how long will each team member be needed? Are any of them now working on other projects? Could they be recalled before this project is completed?
  4. What facilities are needed? Do we have the office space, desks, computers, and meeting rooms that are necessary for the team to work effectively?
  5. Which suppliers will we rely on? What are their skills, availabilities and limitations?

5. Warning signs ignored

The project is failing because the leadership and team are ignoring warning signs of project difficulties. Ask these questions to respond appropriately to project warning signs:

  1. Is the project sponsor repeatedly absent?
  2. Is the project behind schedule?
  3. Is the project trending over budget?
  4. Have multiple project deliverables revealed quality deficiencies?
  5. Are team members leaving the project?
  6. Has the project manager been replaced?
  7. Have members of the project steering committee disappeared or resigned?

6. Communication gaps

The project is failing due to a lack of internal communication about the project. Ask these questions to close communication gaps:

  1. Does the organization have a conceptual understanding of the project, its goal, and its benefits?
  2. Does the project team regularly communicate status and successes through various channels?

7. Scope creep

The project is failing due to well-intentioned acceptance of additional scope, to satisfy key stakeholders, which ultimately overwhelms the team. Ask these questions to adequately address scope creep:

  1. Has the team accepted additional functions or work that can be deferred?
  2. Has the project steering committee urged the project manager to accept additional functions or work that can be deferred?
  3. Has the project implemented and defended a scope management process?

8. Unclear organization

The project is failing because of an unclear project organization without accountability. Ask these questions to adequately address the project organization:

  1. Who is the project sponsor? No one, or more than one, is usually a problem.
  2. Who is the project manager? A self-managed team without a project manager is always a problem.
  3. Who are the members of the project team?
  4. Who are the members of the project steering committee?
  5. Are there more part-time team members than full-time ones?
  6. Are there more consultants on the team than employees?

9. Unrealistic expectations

The project is failing because of unrealistic expectations that exceed the capability of the team and the organization. Ask these questions to adequately understand the unrealistic expectations:

  1. Can the goals and objectives be achieved sensibly with the planned team and budget?
  2. How realistic is the project schedule?
  3. Does the list of risks on the risk register suggest unrealistic expectations?

10. Lack of operational metrics

The project is failing due to a lack of operational metrics that prevent the organization from knowing the accurate status of the project and its progress. Ask these questions to adequately address operational metrics:

  1. Have a few easy-to-measure operational metrics been defined?
  2. Is the data for the operational metrics being routinely collected?
  3. Are the operational metrics being reported regularly?

11. Lack of project visibility

The project is failing due to the lack of project visibility in the minds of the team, stakeholders and the broader organization. Ask these questions to adequately address project visibility:

  1. How well do the team members know the status of other parts of the project?
  2. How well are stakeholders aware of the goal and general status of the project?
  3. Does the project document its decisions and work? Are the associated artifacts easily accessible?

Would you recommend this article?

Thanks for taking the time to let us know what you think of this article!
We'd love to hear your opinion about this or any other story you read in our publication. Click this link to send me a note →

Jim Love, Chief Content Officer, IT World Canada
Previous article3 steps CIOs can take to prevent digital backsliding for business acceleration
Next article5 challenges when going to a headless CMS
Yogi Schulz
Yogi Schulz has over 40 years of Information Technology experience in various industries. Yogi works extensively in the petroleum industry to select and implement financial, production revenue accounting, land & contracts, and geotechnical systems. He manages projects that arise from changes in business requirements, from the need to leverage technology opportunities and from mergers. His specialties include IT strategy, web strategy, and systems project management.