104.2 Project Scoping: Difference between revisions
m add link to 235.2.3 Project Agreements |
mNo edit summary |
||
| Line 12: | Line 12: | ||
|'''Figure''' | |'''Figure''' | ||
|- | |- | ||
|[[media:104. | |[[media:104.2a Project Scoping Process.pdf|project scoping process flowchart]] | ||
|} | |} | ||
|} | |} | ||
| Line 22: | Line 22: | ||
After the elements and limits of a project become clearly defined by the project scoping process, it becomes necessary to develop a [[:Category:235 Preliminary Plans#235.2.3 Project Agreements|project agreement]] if elements of the project are to be shared between the Commission and other public agencies or private interests. | After the elements and limits of a project become clearly defined by the project scoping process, it becomes necessary to develop a [[:Category:235 Preliminary Plans#235.2.3 Project Agreements|project agreement]] if elements of the project are to be shared between the Commission and other public agencies or private interests. | ||
Project scoping should not be thought of as a separate, stand-alone process from the [[:Category:138 Project Development Chronology|project development process]]. It is, instead, the initial stage of the project development process where the details of appropriate solutions are developed. Project scoping begins with the delivery of the need to the project manager and continues until the elements and limits of a project become so well-defined that accurate costs and project delivery schedules can be forecast. A [[media:104. | Project scoping should not be thought of as a separate, stand-alone process from the [[:Category:138 Project Development Chronology|project development process]]. It is, instead, the initial stage of the project development process where the details of appropriate solutions are developed. Project scoping begins with the delivery of the need to the project manager and continues until the elements and limits of a project become so well-defined that accurate costs and project delivery schedules can be forecast. A [[media:104.2a Project Scoping Process.pdf|project scoping process flowchart]] depicting the project scoping process is available. | ||
[[category:104_Scope|104.02]] | [[category:104_Scope|104.02]] | ||
Revision as of 11:03, 15 April 2019
| ||||
|
Project Scoping is a process that is used to clearly define transportation needs and to determine the appropriate means to address them. This involves determining the root causes of the need, developing a range of possible solutions to address the need, choosing the best solution, setting the physical limits of the project, accurately estimating the cost of the project, and forecasting the delivery schedule of the project.
The purpose of project scoping is to develop the most complete, cost effective solutions, as is practical, early in the project development process. This is foundational to avoiding major design changes, large estimate adjustments, and last minute project changes later in the project development process. With proper project scoping, such changes will be minimized and will have reduced impacts on the overall project. Proper project scoping of all needs leads to a more balanced, consistent construction program.
After the elements and limits of a project become clearly defined by the project scoping process, it becomes necessary to develop a project agreement if elements of the project are to be shared between the Commission and other public agencies or private interests.
Project scoping should not be thought of as a separate, stand-alone process from the project development process. It is, instead, the initial stage of the project development process where the details of appropriate solutions are developed. Project scoping begins with the delivery of the need to the project manager and continues until the elements and limits of a project become so well-defined that accurate costs and project delivery schedules can be forecast. A project scoping process flowchart depicting the project scoping process is available.