Project Management Business Documents and Artifacts
PMBOK v8 Definition
Business documents are formal organizational documents that provide context and justification for the project. The two primary business documents are the business case (which justifies the project investment) and the benefits management plan (which defines how and when project benefits will be delivered). These documents are developed outside the project but serve as critical inputs to many project management processes.
Why It Matters for the Exam
The PMI exam frequently tests your ability to distinguish between business documents (created outside the project) and project documents (created during the project). Questions often appear in the Initiating and Planning process groups, asking which document provides justification for a project or how benefits are tracked. Expect situational questions where you must identify the correct document to reference for project approval or benefit measurement.
Key Points to Remember (for the exam)
- Main Business Documents: Business case and Benefits management plan
- Key Input Usage: Business documents are inputs to project charter development and other planning processes
- Critical Project Documents: Assumption log, Issue log, Lessons learned register, Stakeholder register, Risk register
- Common Confusion: Business documents are NOT project documents—they exist before the project starts
- Key Tool for Document Analysis: Expert judgment, Data gathering (brainstorming, focus groups, interviews)
- Output Connection: Project documents are updated throughout the project lifecycle
- Exam Favorite: The assumption log is created early and updated continuously
Typical PMI Exam Example
A project manager is assigned to a new infrastructure project. The sponsor provides a business case and asks the project manager to begin project initiation. Which document should the project manager use to understand the expected financial benefits and justification for the project? → Business case. After approval, which document should be created first to track identified uncertainties? → Assumption log.
PMI Exam Traps
-
Trap: Confusing business case with project charter
- Reality: Business case justifies the project; project charter authorizes the project manager to use resources
-
Trap: Thinking the benefits management plan is a project document
- Reality: It is a business document created outside the project by organizational leadership
-
Trap: Believing the assumption log is only created once
- Reality: The assumption log is continuously updated as assumptions are validated or become constraints
-
Trap: Confusing the issue log with the risk register
- Reality: Issue log tracks problems that have occurred; risk register tracks potential future events
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Charter | Output from business documents | Business case is a key input to developing the project charter |
| Assumption Log | Project document created during planning | Contains assumptions and constraints that feed risk identification |
| Lessons Learned Register | Project document updated throughout | Captures knowledge from previous phases; input to future planning |
| Stakeholder Register | Project document linked to communications | Used in Plan Communications Management and Manage Stakeholder Engagement |
Quick Review Questions
-
Which two business documents are developed outside the project but serve as critical inputs to project initiation?
-
During which process group is the assumption log typically first created?
-
What is the difference between an issue log and a lessons learned register?
-
Which tools and techniques are used to develop project documents during planning processes?
-
When a project manager updates the stakeholder register, which other documents are likely to be updated as well?
PMBOK v8 Reference
Section 2.5 - Project Management Business Documents and Project Documents (Figure 2-35, Figure 2-36, Figure 2-49)