Summary of Project Documents and Project Management Plan
-
Definition:
- Project Documents: Supporting documents created and updated throughout the project, used as inputs or outputs in various processes.
- Project Management Plan: A comprehensive document outlining how the project will be executed, monitored, controlled, and closed.
-
Key Differences:
- Project Documents:
- Dynamic and consistently updated as the project progresses.
- Includes 33 documents such as risk registers, issue logs, and activity duration estimates.
- Project Management Plan:
- Static after approval; changes require a formal change request.
- Contains 18 components such as scope, schedule, cost, and risk management plans.
- Project Documents:
-
Examples of Project Documents:
- Risk Register: Tracks project risks and mitigation strategies.
- Issue Log: Records and monitors project issues.
- Activity Duration Estimates: Helps determine how long tasks will take and informs cost calculations.
- Stakeholder Register: Identifies and documents stakeholder information.
- Assumption Log: Documents project assumptions and constraints.
-
Examples of Project Management Plan Components:
- Scope Management Plan: Defines how the project scope will be managed and controlled.
- Schedule Management Plan: Outlines the approach to creating and managing the project schedule.
- Quality Management Plan: Specifies quality requirements and assurance activities.
- Communication Plan: Details how project information will be shared among stakeholders.
-
Usage Across Processes:
- Project documents and the project management plan are created and referenced throughout the 49 processes.
- Outputs in One Process, Inputs in Another:
- Example: Activity duration estimates (output) from one process inform cost estimates (input) in another.
-
Relevance for Exams:
- Expect questions requiring identification of appropriate documents for specific processes.
- Understand the difference between project documents and the project management plan, including their components and roles.
-
Highlighted Points:
- Dynamic Nature of Project Documents:
- Continuously updated during the project.
- Static Nature of the Project Management Plan:
- Requires formal approval and change requests for updates.
- Integration Across Processes:
- Both documents and the plan are interdependent, with updates in one area influencing others.
- Dynamic Nature of Project Documents:
-
Real-Life Applications:
- Construction: Use activity duration estimates to determine overall project timelines and cost.
- Software Development: Maintain an issue log to track bugs and resolutions.
- Event Planning: Use a stakeholder register to manage communication and involvement.
Key Takeaway:
Project Documents and the Project Management Plan are essential for structured project management. While the plan provides a static framework for execution and control, project documents dynamically support ongoing activities and decision-making. "Plan thoroughly, document consistently, and update intelligently."
No comments:
Post a Comment