Categories: Change Management, Complexity, Expectations Management, Project Delivery, Project Failure, Project Planning, Project Scope, Project Success, Requirements, Timeline
By Marian Haus, PMP
There are dozens of studies about project failure. (To name just three: Standish Group’s Chaos reports, PMI’s 2013 Pulse of the Profession®: The High Cost of Low Performance and Gartner’s 2012 survey on why projects fail). There are at least as many reasons why projects fail.
Although in some cases forces external to a project can imperil its success, I am convinced that properly managing internal factors, particularly scope, is a key enabler for project success. This is because internal factors can be controlled, while external factors can merely be influenced.
Let’s take some classic reasons projects fail and tackle their root causes from a project scope management perspective.
Vague or unclear requirements and no change control—aka the never-ending scope. These are typical problems related to poor project scope management. The remedy is straightforward. Complete and clear requirements should make it to the scope; anything else poses a risk. In addition, at least a basic change management process is required to keep scope creep under control.
Lack of clear roles and responsibilities (R&R). You tailor your project team around the scope work that needs to be carried out. Because of this, you have to be clear about what your project needs to deliver. This includes product specifications, product design, implementation, integration with other related product parts, validation, delivery, etc.
If the lack of R&R clarity lies within your client organization or with an organization external to your project, then break down your project scope into specific deliverables and lay out the assumption and prerequisites for delivering them. For example, a product specification will have to be reviewed and signed off by the client, the client is expected to provide you with the validation benchmarks, etc.
A lack of R&R often results in lack of ownership and accountability of deliverables.
Underestimated timelines. This can happen especially if estimations are done based on insufficient information or when the scope is not well understood. Estimates are consequently rough, based on previous experience, approximations and assumptions. If conditions are changing during the project lifecycle, this can lead to time or budget overruns.
Unclear and/or unrealistic expectations. This is often related to the project scope. Your project team might be unclear about what it is supposed to deliver or what level of quality and maturity your deliverable will have to pass to meet the acceptance criteria. In other cases, the team might be unclear on how the delivery of your project scope will impact the receiving organization.
Project complexity. This relates mainly to the failure to break down a large scope into more manageable pieces and deliverables. If the list of deliverables is not clear, the sequence in which these are to be produced will not be determined. If the deliverables’ relation to each other isn’t clear, then team members will just be busy delivering something, sometime, for some level of effort. This leads to missing the project goal or ending up with time or budget overruns.
A well-understood and executed scope brings you a huge step closer to finishing your project successfully.
What is your experience with managing project scopes? What key factors, other than scope, do you see as enablers for project success?