Find out why your project is failing

[metoc15411]

While Dilbert struggles with a spiky boss and a company with functional problems, sometimes the cause of a project's problems isn't immediately obvious. Even the best project managers - with great project plans, adequate budgets, and fantastic scope control - sometimes experience project failure.

Why? Answering this question is the goal of the second step.

When project managers reach this step, surface-level answers are often a temptation. They may focus on the complexity of their project, outdated project management software , unclear goals, or lack of stakeholder engagement, but these issues are so general that they don’t provide enough insight to create real solutions.

Ask why. Why are the goals unclear? Why aren't users engaged? Be specific when answering these questions. Consider using the lean management technique of the " five whys " to answer these tough questions.

Of course, some of these answers may be hard to hear gcash database and the solutions may range from difficult to impossible. Remember: if these problems were easy to fix, they would be addressed and solved. Even simple problems - like a team member leaving - can take months. Ask yourself: Are you using the right technology for the job? Are your dependencies so external that you simply don't have control over the project?

If you're still trying to figure out what's causing your project to fail, consider these seven issues. They tend to be the most common reasons for project failure.

Complexity
External
Financial
Operational
Organizational
Schedule
Technology
Then take the time to determine what risks you face in trying to save the project. Is it worth the risk? Can the project be saved? Answer these questions before moving forward.

Key activities: Identify feasible solutions to save the project (including terminating the project), identify the root causes of the problem, and identify risks to continuing the project.

Step 3: Set up the war room
Project failure

Okay, General. This is your thing. You assemble your team, seat them all together, and work in the salvage room. You're in a kill-or-fix mentality - you've finished your fact-finding, you've asked for further research, or you've found other excuses to delay the process. All of that should have been done in Phase 2. You're ready to figure out what the hell to do with your project.

The War Room will be intense. The decision-making process may take two hours, a full day, or, in rare cases, a full week. All key decision makers must be present . I understand that this may not be possible, especially if the project is scheduled to last a full day. Some managers may prefer to be called in as the meeting draws to a close, when team members can present prepared options (such as “kill” or “worst case”).

To get the most out of the workshop, take the meeting offline. If possible, conduct the entire meeting face-to-face or, if necessary, via web conferencing software . Try to limit the meeting to ten people, including the most important stakeholders (such as sponsors), the project manager, senior team members, and perhaps a technical representative to provide feedback on the feasibility of the plan.