Artifacts: Options for Deliverables, Work Organization, and Collaboration

PMBOK v8 Definition

Artifacts illustrate the range of options project teams can use to produce deliverables, organize work, and enable communication and collaboration. They are presented in Section 4 of the PMBOK® Guide, which describes commonly used models, methods, and artifacts that project teams can employ throughout the project life cycle.

Why It Matters for the Exam

The concept of artifacts appears frequently in PMI exam questions testing your understanding of the tools and outputs project teams use to manage work. Questions often ask you to identify which artifact is appropriate for a specific situation, or to distinguish between different types of artifacts used for producing deliverables versus organizing work versus enabling communication.

Key Points to Remember (for the exam)

• Core Purpose: Artifacts serve three primary functions—producing deliverables, organizing work, and enabling communication and collaboration
• Range of Options: Artifacts are not mandatory; they represent choices project teams can select based on project needs
• Accepted Deliverables: These are products, services, and capabilities created through a project that are validated by an appointed individual or group against established criteria
• Tailoring Connection: The selection and use of artifacts is part of tailoring—the deliberate adaptation of the project management approach, governance, and processes to align with the project's environment and objectives
• Team Agreements: A specific type of artifact representing behavioral parameters and working norms established by the project team and upheld through individual and team commitments
• No Prescriptive List: Artifacts appear in alphabetical order in Section 4, indicating they are reference options rather than mandatory requirements
• Performance Domain Integration: Artifacts support all seven project management performance domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk

Typical PMI Exam Example

A project team is beginning a new software development project and needs to establish how team members will interact, make decisions, and resolve conflicts. The project manager recommends creating a document that defines behavioral parameters and working norms. What type of artifact should the team create?

Answer: Team agreements—a set of behavioral parameters and working norms established by the project team and upheld through individual and team commitments.

PMI Exam Traps

• Trap: Thinking artifacts are mandatory for every project

  • Reality: Artifacts illustrate the range of options—teams tailor their use based on project needs

• Trap: Confusing artifacts with processes or performance domains

  • Reality: Artifacts are the outputs/templates used within processes, not the processes themselves

• Trap: Assuming artifacts are created only at project start

  • Reality: Artifacts like team agreements should be created at the beginning, but many artifacts evolve throughout the project

• Trap: Treating all artifacts as equally relevant to all three functions

  • Reality: Some artifacts primarily support producing deliverables, others focus on organizing work, and others enable communication and collaboration

Important PMI Connections

Quick Review Questions

1. What three primary functions do artifacts serve according to PMBOK v8?

2. A project team is deciding whether to use a formal project charter or a simpler kickoff presentation. What PMBOK v8 concept describes this decision-making process?

3. When should team agreements typically be created, and what do they establish?

4. How do artifacts relate to the seven project management performance domains?

5. What is the difference between an artifact used for producing deliverables versus one used for enabling communication and collaboration?

PMBOK v8 Reference

Section 4 - Models, Methods, and Artifacts (described in the introductory text as illustrating the range of options project teams can use to produce deliverables, organize work, and enable communication and collaboration)

Also referenced in:

• Section 3 - Tailoring (tailoring process considers development approach, processes, project life cycle, deliverables, and stakeholder/team involvement)
• Section 1 - Project Management Performance Domains (seven interactive domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk)
• Section 4 - Accepted Deliverables (products, services, capabilities validated against established criteria)
• Section 3.8 - Team Agreements (behavioral parameters and working norms established by the project team)