
Project Management Plan, Project Documents, and Organizational Process Assets
PMBOK v8 Definition
The Project Management Plan is the document that defines how the project is executed, monitored, controlled, and closed. Project Documents include all components such as the project scope statement, requirements documentation, lessons learned register, project schedule, risk register, stakeholder register, and team charter. Organizational Process Assets are the policies, procedures, regulations, and historical information from previous projects that influence how the current project is managed.
Why It Matters for the Exam
This triad of inputs appears in nearly every process across all Knowledge Areas on the PMI exam. Questions frequently test your ability to distinguish which items belong to the Project Management Plan versus Project Documents versus Organizational Process Assets. Expect scenario-based questions asking what input is missing for a specific process, or which document should be updated after a change.
Key Points to Remember (for the exam)
-
Main Input Categories: The three primary input categories across all processes are Project Management Plan, Project Documents, and Organizational Process Assets (plus Enterprise Environmental Factors)
-
Project Management Plan Components: Scope management plan, quality management plan, communications management plan, stakeholder engagement plan, financial management plan, scope baseline
-
Project Documents Components: Requirements documentation, stakeholder register, lessons learned register, project schedule, risk register, resource requirements, team charter, issue log, work performance reports
-
Organizational Process Assets: Policies, procedures, regulations, historical information, lessons learned from previous projects, templates, standard processes
-
Key Distinction: Project Management Plan is a formal, approved document that undergoes change control. Project Documents are working documents that can be updated more informally. Organizational Process Assets exist outside the current project.
-
Common Confusion: The scope baseline (scope statement + WBS + WBS dictionary) is part of the Project Management Plan, NOT Project Documents
-
Critical Exam Point: When a process lists "Project documents – All components" as an input, it means any relevant project document can serve as input, not just specific ones
Typical PMI Exam Example
You are managing a construction project and need to estimate costs. The project manager reviews the quality management plan and scope baseline from the Project Management Plan, along with the lessons learned register, project schedule, resource requirements, and risk register from Project Documents. Which input category is missing? Answer: Organizational Process Assets (historical cost data from previous similar projects)
PMI Exam Traps
-
Trap: Confusing the scope baseline with project documents
-
Reality: The scope baseline (scope statement, WBS, WBS dictionary) is part of the Project Management Plan, not Project Documents
-
Trap: Thinking all project documents are part of the Project Management Plan
-
Reality: Project Documents and the Project Management Plan are separate categories. The PMP is the formal plan; documents are supporting details
-
Trap: Treating Organizational Process Assets as project-specific documents
-
Reality: OPAs exist at the organizational level, not the project level. They include policies, procedures, and historical information from past projects
-
Trap: Assuming approved change requests are always project documents
-
Reality: Approved change requests appear as separate inputs in many processes (e.g., Monitor and Control Scope) and are distinct from regular project documents
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Enterprise Environmental Factors | Parallel input category | EEFs are external factors; OPAs are internal organizational assets |
| Scope Baseline | Component of PMP | Contains scope statement, WBS, and WBS dictionary |
| Approved Change Requests | Input to multiple processes | Flow from Perform Integrated Change Control into execution processes |
| Quality Metrics | Output becomes input | Quality metrics are created in Plan Quality Management, then used in Monitor and Control Scope |
Quick Review Questions
-
In the Estimate Costs process, which components of the Project Management Plan are listed as inputs?
-
A project manager needs to review the stakeholder register and requirements documentation. Are these part of the Project Management Plan or Project Documents?
-
During Monitor and Control Scope, what are the three categories of inputs from organizational assets?
-
What is the difference between Organizational Process Assets and Enterprise Environmental Factors in terms of control?
-
When a process lists "Project documents – All components" as an input, what does this mean for the project manager?
PMBOK v8 Reference
Section 2.5 - Project Management Plan and Project Documents Section 2.6 - Organizational Process Assets Various process figures showing inputs across Knowledge Areas (Figures 2-4, 2-35, and process-specific diagrams)