Process of subdividing project deliverables and project work into smaller, more manageable components. The key benefit of of this effort is provides a structured vision of what has to be delivered during the Define Phase.
Subdividing project deliverables and project work into smaller, more manageable components.
The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The WBS organizes and defines the total scope of the project, and represents the work specified in the current approved project scope statement.
The planned work is contained within the lowest level of WBS components, which are called work packages. A work package can be used to group the activities where work is scheduled and estimated, monitored, and controlled. In the context of the WBS, work refers to work products or deliverables that are the result of activity and not to the activity itself.
Process and Procedures:
Process Verification Record(s)
- Maintained By: <?>
- Submitted By: <?>
- Frequency of Submission: <?>
Project Plan covers activities related to following areas:
- Project Planning
- Project Monitoring and Control
- Risk Management
- Supplier Agreement Management
- Integrated Project Management
Project Planning enables the Project Manager to make reasonable estimates of resources, costs and schedules, thereby establishing and maintaining plans that define project activities. The Project Manager shall develop detailed plans for all project phases in the project.
Project Monitoring provides adequate visibility into the progress of the project. This enables appropriate corrective actions to be taken if the project’s performance deviates significantly from the plan. The Project Manager shall monitor and track the project as per the project monitoring meetings planned in the Project Plan.
Integrated Project Management includes determining and establishing integrated teams, and distributing requirements, responsibilities, authorities, tasks and interfaces to teams. The Project Manager shall ensure that the sub-teams collaborate and work towards the single project goal.
1.1 Develop Preliminary Project Plan [PP(P)]
Project Manager shall develop the preliminary project plan for the Define phase before the Plan phase tollgate. Using the conventional estimation process, the Project Charter baseline shall be used as the basis for developing estimates for the Define phase. The Project Manager shall develop the detailed effort estimates for the Define phase (or for the Plan and Define phase if using the alternate GM Bottom-up Estimation tool approach), which contains effort for developing Business Requirements Document (BRD), System Requirements Specifications (SRS) and Architectural Design Document.
There may be a need to develop prototype in the Define phase to verify the requirements. Refer to Prototype Plan to develop the plan for creation of prototype. Estimates to develop the prototype and the rest of the Define phase shall be documented in the Estimation Report for the Define Phase or the GM Bottom Up Estimation Tool.
If the System Deployment Manager is not assigned for the project, the Project Manager shall identify the individual who will assume the role of the project’s Deployment Representative. This person shall act as the liaison with the Regional Deployment Organization and provide information on non-functional requirements for the development of SRS work product.
Refer to the Develop Detailed Plan section in this process for documenting the Preliminary Project Plan for the project.