4.6.

9  OTHE R ARTIFACTS
The documents and deliverables described here do not fit into a specific category; however,
they are important artifacts that are used for a variety of purposes.
▶ Activity list. This document provides a tabulation of schedule activities that shows the
activity description, activity identifier, and a sufficiently detailed scope of work description
so project team members understand what work is to be performed.
▶ Bid documents. Bid documents are used to request proposals from prospective sellers.
Depending on the goods or services needed, bid documents can include, among others:
▹ Request for information (RFI),
▹ Request for quotation (RFQ), and
▹ Request for proposal (RFP).
▶ Metrics. Metrics describe an attribute and how to measure it.
▶ Project calendar. This calendar identifies working days and shifts that are available
for scheduled activities.
▶ Requirements documentation. This document is a record of product requirements and
relevant information needed to manage the requirements, which includes the associated
category, priority, and acceptance criteria.
▶ Project team charter. This document records the project team values, agreements,
and operating guidelines, and establishes clear expectations regarding acceptable behavior
by project team members.
▶ User story. A user story is a brief description of an outcome for a specific user, which
is a promise of a conversation to clarify details.

4.7  ARTIFAC T S AP P L IE D A C R O S S P E R F O R M A NC E DO M A I NS
Different artifacts are more likely to be useful in different performance domains. While the
delivery approach, product, and organizational environment will determine which artifacts are most
applicable for a specific project, there are some performance domains that are more likely to make
use of specific artifacts. Table 4-3 suggests the performance domain(s) where each artifact is more
likely to be of use; however, the project manager and/or project team has the ultimate responsibility
for selecting and tailoring the artifacts for their project.

192 PMBOK ® Guide

 Table 4-3. Mapping of Artifacts Likely to Be Used in Each Performance Domain

Performance Domain

Measurement
Stakeholders

Project Work
Dev Approach
and Life Cycle

Uncertainty
Planning

Delivery
Artifact

Team
Strategy Artifacts:
Business case X X
Project brief X X
Project charter X X
Project vision statement X X
Roadmap X X X
Log and Register Artifacts:
Assumption log X X X X
Backlog X X X
Change log X X
Issue log X
Lessons learned register X
Risk-adjusted backlog X X
Risk register X X X X
Stakeholder register X X
Plan Artifacts:
Change control plan X X X
Communications management plan X X X
Cost management plan X
Iteration plan X
Procurement management plan X X
Project management plan X X X
Quality management plan X X X
Release plan X X
Requirements management plan X X
Resource management plan X X
Risk management plan X X X
Scope management plan X X

Section 4 – Models, Methods, and Artifacts 193

 Table 4-3. Mapping of Artifacts Likely to Be Used in Each Performance Domain (cont.)

Performance Domain

Measurement
Stakeholders

Project Work
Dev Approach
and Life Cycle

Uncertainty
Planning

Delivery
Artifact

Team
Schedule management plan X X X
Stakeholder engagement plan X X
Test plan X X X X
Hierarchy Chart Artifacts:
Organizational breakdown structure X X X
Product breakdown structure X X
Resource breakdown structure X X X X
Risk breakdown structure X X
Work breakdown structure X X X
Baseline Artifacts:
Budget X X X
Milestone schedule X X X X
Performance measurement baseline X X X X
Project schedule X X X
Scope baseline X X X X
Visual Data and Information Artifacts:
Affinity diagram X X
Burn chart X X X
Cause-and-effect diagram X X X
Cycle time chart X X
Cumulative flow diagram X X
Dashboard X X
Flow chart X X X
Gantt chart X X X
Histogram X
Information radiator X X
Lead time chart X X
Prioritization matrix X X X

194 PMBOK ® Guide

 Table 4-3. Mapping of Artifacts Likely to Be Used in Each Performance Domain (cont.)

Performance Domain

Measurement
Stakeholders

Project Work
Dev Approach
and Life Cycle

Uncertainty
Planning

Delivery
Artifact

Team
Project schedule network diagram X X
Requirements traceability matrix X X X
Responsibility assignment matrix X X
Scatter diagram X X X
S-curve X X
Stakeholder engagement assessment matrix X X X
Story map X X
Throughput chart X X
Use case X X
Value stream map X X X
Velocity chart X X
Report Artifacts:
Quality report X X X
Risk report X X
Status report X
Agreements and Contracts:
Fixed-price X X X X X X
Cost-reimbursable X X X X X X
Time and materials X X X X X X
Indefinite time indefinite quantity (IDIQ) X X X X X X
Other agreements X X X X X X
Other Artifacts:
Activity list X X X X
Bid documents X X X
Metrics X X X
Project calendars X X X
Requirements documentation X X X X
Project team charter X X
User story X X X

Section 4 – Models, Methods, and Artifacts 195