Project Artifact: Document Created to Manage a Portfolio, Program, or Project
PMBOK v8 Definition
A project artifact is a document or other item created during a portfolio, program, or project to help manage it and provide information to the project team, stakeholders, and management. Artifacts include any document, template, output, or deliverable produced throughout the project life cycle. They serve as evidence of project activities, decisions, and progress, and are essential for communication, governance, and historical reference.
Why It Matters for the Exam
The concept of artifacts appears frequently on the PMI exam, particularly in questions about project documents, project management plans, and deliverables. The exam tests your ability to distinguish between different types of artifacts, their purposes, and when they are created or updated. Expect scenario-based questions where you must identify which artifact is appropriate for a given situation or which artifact is an input or output of a specific process.
Key Points to Remember (for the exam)
- Definition: Artifacts are documents or items created to help manage a portfolio, program, or project and provide information to the team, stakeholders, and management.
- Purpose: They support communication, decision-making, governance, and historical reference across the project life cycle.
- Types of Artifacts:
- Project management plan: The comprehensive plan that guides execution, monitoring, and closure.
- Project documents: Supporting documents like the project charter, stakeholder register, risk register, and schedule.
- Deliverables: Any unique and verifiable product, result, or capability produced.
- Common Confusion: Artifacts are often confused with deliverables. Artifacts include all project documents and items created for management purposes, while deliverables are the specific outputs produced for the customer or sponsor.
- Progressive Elaboration: Many artifacts are refined iteratively as more information becomes available (e.g., the project management plan is progressively elaborated).
- Governance Link: Artifacts support project governance by providing the framework, functions, and processes that guide project management activities.
- Life Cycle Applicability: Artifacts exist across all project phases and are created, updated, and archived throughout the project.
Typical PMI Exam Example
Scenario: A project manager is preparing the project management plan and needs to document how changes to project scope will be handled. Which artifact should the project manager create?
Answer: The change management plan, which is a subsidiary plan within the project management plan that defines the process for managing change requests.
PMI Exam Traps
- Trap: Confusing a project artifact with a deliverable.
- Reality: Artifacts include all documents and items created for management (e.g., risk register), while deliverables are the final outputs for the customer (e.g., software product).
- Trap: Thinking artifacts are only created once and never updated.
- Reality: Many artifacts are progressively elaborated and updated throughout the project as more information becomes available.
- Trap: Assuming all artifacts are part of the project management plan.
- Reality: The project management plan is one type of artifact; other artifacts include project documents (e.g., stakeholder register, lessons learned register) and deliverables.
- Trap: Believing artifacts are only for the project team.
- Reality: Artifacts provide information to stakeholders, management, and the project team—they serve multiple audiences.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Management Plan | Type of artifact | The plan is the primary artifact guiding execution; its subsidiary plans are also artifacts. |
| Project Documents | Subset of artifacts | Includes registers, logs, and lists (e.g., risk register, issue log, stakeholder register). |
| Deliverables | Output of processes | Deliverables are artifacts produced for the customer; they are verified and validated. |
| Progressive Elaboration | Process applied to artifacts | Artifacts like the project management plan are refined iteratively as details emerge. |
| Project Governance | Framework using artifacts | Governance defines how artifacts are created, approved, and used to guide project activities. |
Quick Review Questions
- A project manager creates a document that lists all identified risks and their responses. What type of artifact is this?
- During which process group are artifacts like the project charter and stakeholder register typically created?
- What is the difference between a project artifact and a deliverable?
- Why is progressive elaboration important for artifacts like the project management plan?
- Which artifact provides the framework, functions, and processes that guide project management activities?
PMBOK v8 Reference
Section 2.4 – Project Artifacts (The Standard for Project Management, PMBOK v8)
Note: The exact section number may vary slightly in your edition; the concept is covered under the definition of project artifacts and their role in managing portfolios, programs, and projects.