Project Management Framework
Initiation - Scope
Definition
The project scope states what will and will not be included as part of the project. Scope provides a common understanding of the project for all stakeholders by defining the project's overall boundaries. Scope can be defined in terms of impacted organizations, processes, systems, data, functionality and the like. Use collected project requirements to test the scope statement.
Why is this important?
Proper scope definition is critical to a project's success. It establishes the boundaries of what the project will and will not accomplish. The scope statement eliminates any confusion or ambiguity that might still exist after considering the project's goal, objectives and high-level deliverables statements. Poorly defined scope leads to changes in collected project accomplishments (scope creep). These changes inevitably lead to increased work effort, which in turn causes project delays, cost overruns, poor team morale and/or customer dissatisfaction. Clearly defined scope will crystallize realistic stakeholder expectations. Additionally, a clear statement of scope is the foundation for defining a change management strategy. Using a change management process, changes to scope can be managed, rejected, or deferred in a disciplined manner.
Instruction
To avoid confusion, write the scope statement in clear and narrow terms. Provide a statement of the processes, internal entities, systems, customers, and outside entities that will (or will not) be part of the project. Cross-reference the scope statement, project objectives and project deliverables for consistency. If these items aren't consistent, this may indicate poor scope clarity.
How to scale
Since the scope statement sets project boundaries it's important to identify all possible entities and processes impacted by the project. Detailed scope statements define what is included in the project and excluded from the project for each identified entity and process.
Related Links:
Scope Examples
Checklists