- Project Charter (in.)
- Requirements Specification
- Integrated Project Plan (co.)
Scope Planning
What is the project objective and what does the project contain? What surrounding conditions need to be considered?
The Scope Planning Process identifies all products and services relevant to the project. This includes expectations, priorities and compromises (concerning time planning, budget, quality and functionality) as well as products and services, which do not directly belong to the project (i.e. items outside of the project scope).
Input
Process Steps
1. Review of existing documentation
For a detailed project scope, the documents from the initiation phase are required.
2. Developing scope statement
The scope statement is a major project document. It may serve as a tool for defining, documenting, discussing and reviewing the project scope. It also aims at gaining commitment to and common understanding for the project scope and project objectives. Therefore, all stakeholders need to understand the scope. Also relevant topics that are outside of the project scope need to be documented.
3. Defining the project procedure (phases)
The project procedure embodies the strategy by which to fulfill the project objectives. The final decision to adopt a certain project procedure calls for a prior consideration of the planning results from the other knowledge areas.
4. Reviewing and requesting approval for the scope statement
The scope statement needs to be reviewed if it does the SMART-principle justice. If deemed necessary, adjustments are to be made. All stakeholders are required to fully approve the updated scope statement.
S –> pecific M –> easurable A –> greed on (Achievable) R –> ealistic (Relevant) T –> imely
5. Developing work breakdown structure
Based on the scope statement and project procedure, the required work packages are defined and structured. The work breakdown structure covers all steps that are necessary to complete the project and deliver the agreed standard of performance.
Please also see knowledge area “Integrated Planning” for overall project planning.
Work Breakdown Structure
The work breakdown structure displays a hierarchical structure of the necessary steps and tasks to produce the project results. Thereby it facilitates the detailed planning of all other knowledge areas and the effective monitoring and controlling of the project.
Rules to develop the Project Plan Level 1:
- Begin the project plan on the highest level, and copy in the project phases, defined in the initiation phase (-> Project Procedure).
- Subdivide, step by step, all required deliverables of the respective process phases, into smaller, more manageable work packages.
- Continue to break down work packages into more manageable components until you’re able to clearly determine the required effort and assign responsibilities correspondingly.
- Be sure that the whole project is subdivided into smaller components and that 100% of the work packages necessary to produce the project outputs are included (the project plan should not include any work that falls outside the actual scope of the project). Hence, all activities planned within a respective knowledge area need to be added to the work breakdown structure on a regular basis.
| Type | Name |
| Phase | Initiation |
| Work Package | Work Package 1 |
| Activity | Activity 1 |
| Activity | Activity 2 |
| Work Package | Work Package 2 |
| Activity | Activity 1 |
| Activity | Activity 2 |
| Milestone | Milestone 1 |
| Phase | Planning |
| Work Package | Work Package 1 |
| Activity | Activity 1 |
| Activity | Activity 2 |
| Work Package | Work Package 2 |
| Activity | Activity 1 |
| Activity | Activity 2 |
| Milestone | Milestone 2 |
