View free policies procedures examples from all manuals. No obligation, no credit card!
There are a number of things that can and do go wrong on a project. You are probably familiar with many of the most common project management nonconformances or failures.
Common Project Management Nonconformances
- Errors, omissions or just plain poor assumptions
- Delays which affect the project schedule or the originator’s ability to meet project deadlines
- Late submissions
- Unauthorized changes to projects, schedules, plans, etc.
- Non-compliance with established policies, procedures, specifications or project specific Quality Assurance Plans
- Cost overruns (which result from all other failures)
You don’t have to be a project manager to understand that anything which negatively impacts the project delivery system or a specific project’s quality, schedule, or budget is a problem. These are all symptoms of a larger set of problems.
So just what are the
Root Causes of Project Failures?
1. Bad Communications.
Project management is all about good communications. You have to keep everyone informed about changes, assumptions, requirements, standards, budgets, costs, and the schedule. Developing a good visual management system is a tremendous benefit to any project manager. Paper systems in binders is a notoriously bad way to keep people informed. Develop a good communication system and you will reduce the risk of project failure.
2. Poor Schedule or Resource Management (Mismanagement).
Managing a project is really about managing the schedule, but a schedule is really a collection of resources that are being managed on a schedule. Mismanage your resource schedule and you increase the chances of your project failing.
3. Weak Requirements Definitions (leads to inadequate planning).
If you don’t know where you are going then how do you know when you get there? A good project manager must know what the target is. Your project requirements are the target. One way of defining requirements is to describe what the end result looks like in measureable or object terms. Instead of requiring software to be friendly or easy to use, how about saying that it has to be simple enough that a 12 year old child can use it. We can argue about “easy to use” software but at least we now have an objective measure for our testing.
4. Inadequate Planning, Assumptions, Risks, or Resources.
If you are planning a project, then you should be familiar with Murphy’s Law, “If anything can go wrong it will.” Projects are frequently impacted by risks, assumptions about resource usage, or plain old surprises. The traditional solution is to add safety time or buffers to tasks to allow for schedule slippage and unplanned events. There are a lot of reasons why this fails too. I would suggest implementing Critical Chain management to take more control over these buffers and not let them slip away.
5. Use of New or Unproven Technologies / Methods.
It can be so tempting to use the latest technology, or new method, but unless you are trained on the newest thing, all you are doing is introducing new risks. Projects have enough risks already without the need to introduce new risk from unproven technology.
6. Ineffective (or Nonexistent) Quality Controls.
Quality control is a simple system of checks and balances to ensure you are delivering what the customer asked for in the first place. What kind of quality control are you using for your project management? Are you tracking every project management nonconformance? Charting to find trends? Taking action when the trend is outside the norm? Most projects have a system for correcting problems but this is not the same as a system of corrective action. Project failures result from ineffective quality controls.
7. Managing Multiple Projects at Once or Multitasking Resources.
It seems so obvious to recapture downtime and juggle a few extra tasks in the meantime. But multitasking introduces complexity and schedule risk, which can impact all projects involved. Less is more. Focus is power. You can actually increase your productivity by focusing on fewer projects.
8. Supply Chain Failures.
Sometimes you have to contract out the work. But managing contractors has inherent risks too. Contractors may not have the skill level required for the task. Contractor’s multi-task in order to stay busy, and multitasking introduces complexity and schedule risk. It sounds so easy to contract out some of the work to your supply chain but it actually adds to complexity unless you have clearly defined requirements agreed to first.
9. Scope Creep or Poor Impact Analysis.
This happens on practically every project doesn’t it? You start with a clear concept or at least you thought it was clear when you started. Then one thing leads to another and before you know it you are involved in a different project. That’s scope creep. If we are doing “A” then we must do “B” and if we are do “B” then we have to also do “C”. Clarifying the real requirements and performing a good impact analysis are two methods to solve this problem. Otherwise, scope creep will impact your schedule, your budget, and your resources.
10. Lack of Qualified Resources.
“We will just have to make do.” If you hear this then you know you are questioning your resources. Give the wrong task to the wrong person and you are impacting your project. This usually happens because we lack enough experienced resources.
There you have it, the top ten project management failures. Individually, you might be able to manage around any single cause but taken collectively, you will have a colossal project management failure. In fact, any two could seriously impact any project. Don’t let this happen to you; learn how to prevent the…
Causes of Project Management Failure
- Bad Communications
- Poor schedule or resource Management (mismanagement)
- Weak requirements definitions (leads to inadequate planning)
- Inadequate planning, assumptions, risks, or resources
- Use of new or unproven technologies/methods
- Ineffective (or nonexistent) quality controls
- Managing multiple projects at once or multi-tasking resources
- Supply chain failures
- Scope creep or poor impact analysis
- Lack of qualified resources