What is the leading cause of cost and schedule overruns?
The level of scope definition in a project is the greatest driver of cost and schedule certainty.
Front End Planning
Front end planning is often considered the single most important process in the capital project life cycle. It is focused on achieving sufficient scope definition to address risk and make a decision to committing resources that will maximize the potential for project success
Front end planning is known by many other names including:
[list type=”check”]
- Front end loading, or FEL
- Pre-project planning, and
- Project development just to name a few
[/list]
This process is generally defined in three main phases:
CII Stage Gates in Front End Planning
Feasibility, which is primarily focused on
[list type=”check”]
- defining business objectives and
- identifying potential alternatives
[/list]
Concept, concerned with
[list type=”check”]
- evaluating and selecting the best alternative
[/list]
Detailed scope, which is focused on
[list type=”check”]
- defining the technical scope of the project,
- further developing project execution plans, and
- developing a cost estimate and schedule for project authorization
[/list]
Simply put, front end planning involves:
[list type=”check”]
- Performing the right project
- Scoping out the right product
- Selecting the right way to execute
[/list]
Scope definition refers to documenting this scope of work to form an organized plan.
Reasons for Poor Scope Definition
It is intuitive that starting execution with a well-defined scope should improve project results. Nevertheless, there are some common misconceptions and behaviors that lead to poorly defined scope.
The top five reasons or behaviors that contribute to poor scope definition include:
1. Pressure to get product to market faster.
A common misconception is that you’ll get product to market faster by compressing every phase, including the planning effort.
We’ve seen this surface through statements like:
[list type=”check”]
- “front end planning will just slow down this project”, or
- “we’re on a fast-track schedule”
[/list]
2. Restricting key resource involvement.
As an example, we have worked with organizations where Operations & Maintenance resources are stretched very thin. Their culture has evolved such that Operations & Maintenance will openly admit that they only assign resources to a capital project once funding and approval of the project is a sure thing. The opportunity cost for the organization is that key scope requirements are missed during front end planning from a lack of involvement of these key resources.
3. Lack of in-house design or planning capability.
Owners can successfully address this issue by engaging specialized consultants and engineers. However, the challenge is to ensure the owner’s team remains active in planning throughout the project and doesn’t simply hand off the planning effort to the contractor and then disengage.
4. Overly optimistic leadership
This is commonly seen with projects that appear on the surface to repetitive and lead to optimistic statements like “this will be simple. We’ve done this hundreds of times.”
5. Financial pressure to minimize planning costs
Without a doubt, it’s a careful balancing act to ensure you don’t overspend on front end planning for projects that end up getting cancelled. One of the main benefits of a well-defined front end planning process with gate reviews is to identify projects that don’t meet your strategic objectives and cancel these as early as possible.
However, projects that proceed beyond the early gate reviews need sufficient funding to ensure a well-defined scope is achieved.
The Final Question…
With an understanding of the major contributors to poor scope definition, it raises the question when we look at our past projects: