Ads 468x60px

Thursday 26 April 2012

Project Management Plan

What is Project Management Plan???

In terms of project management in planning process, a Project Management plan is the most important document that needed to perform work. The project management plan is the sole outputs of develop project management plan in integration management. 

Project Management Plan is a formal and approved document that defines how the project is executed, monitored and controlled. It may be in a form of an executive summary or a detailed document, and it may compose one or more subsidiary management plans and other planning documents
Project plan is used to:
  • Guide project execution
  • Document project planning assumption
  • Document project planning decision based on the selected alternatives
  • Facilitate communication among stakeholders
  • Define key management review 
  • Provide a baseline for progress measurement and project control
The keys to understanding the project management plan:
  1. The project management plan is formal. It is important to think of the project management plan as a formal, written piece of communication.
  2. The project management plan is a single document. It is not 15 separate plans. One those separate documents are approved as the project plan, they become a single document.
  3. The project management plan is approved. In other words, there is a point in time at which it officially becomes the project plan. Who approves it is going to differ based on the organizational structure and other factors, but typically it would be the project manager, the project sponsor, the functional managers who are providing resources for the project.  
  4. The project management plan defines how the project is managed, executed, and controlled. This means that the document provides the guidance on how the bulk of the project will be conducted.
  5. The project management plan may be summary or detailed. 
Components of Project Management Plan:
  • Change Management Plan
  • Configure Management Plan
  • Scope Management Plan
  • Time Management Plan
  • Cost Management Plan
  • Quality Management Plan
  • Process Improved Plan
  • Human Resources Plan
  • Communication Management Plan
  • Risk Management Plan
  • Procurement Management Plan
  • Requirements Management Plan
  • Scope Baseline
  • Cost Performance Baseline
  • Schedule Baseline

 

Project Scope Management



Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.

Remember, Scope Management means:
- Constantly checking to make sure all the work are completed
- No additional work include in the Project Charter
- Preventing extra work or gold platting

Process in Project Scope Management:
1. Collect Requirements, the process of defining and documenting stakeholder’s needs to 
     meet the project objectives
 
     Key Inputs: Stakeholder Register
     Key Tools & Techniques:  Facilitated Workshops, Group Creativity Techniques
     Key Outputs: Requirement Documentation, Requirement Traceability Matrix
 
2.  Define Scope: the process of developing a detailed description of project and product
     
     Key Inputs:Project Charter, Requirement Documentations
     Key Tools & Techniques:  Alternatives Identification
     Key Outputs: Project Scope Statement

3.  Create WBS: the process of subdividing project deliverable and project work into smaller 
     and more manageable components

     Key Inputs:Project Scope Statement
     Key Tools & Techniques:  Decomposition
     Key Outputs: WBS, WBS Dictionary, Scope Baseline

4.  Verify Scope: the process of formalizing acceptance of the completed project deliverable

     Key Inputs:Project Management Plan
     Key Tools & Techniques:  Inspection
     Key Outputs: Accepted Deliverable, Change Request

5.  Control Scope: the process of monitoring project status, product scope, and managing 
     changes 

     Key Inputs:Project Management Plan, Work Performance Information
     Key Tools & Techniques:  Variance Analysis
     Key Outputs: Work Performance Measurements

Differences between Verify Scope and Perform Quality Control
Verify Scope:
- Is often performed after Perform Quality Control
- Is primarily concerned with completeness
- Is concerned with the acceptance of the product by the project manager, the sponsor, the 
  customer and others

Perform Quality Control:
- It is not unusual for these processes to be performed at the same time
- Is primarily concerned with correctness
- Is concerned with adherence to the quality specification
 
Important Note: 
If the project is canceled before completion, Verify Scope should be performed to document
where the product was in relation to the scope at the point when the project ended 
 
 


 

Lijit’s search

Business Online

Popular Post