Models, Methods, and Artifacts: Options for Deliverables, Work, and Collaboration

PMBOK v8 Definition

Models, methods, and artifacts illustrate the range of options project teams can use to produce deliverables, organize work, and enable communication and collaboration. These are presented in Section 4 of the PMBOK® Guide as commonly used approaches that project teams can select and tailor to fit their specific project environment. The selection of appropriate models, methods, and artifacts is driven by the guiding project management principles and the tailoring considerations established at the beginning of the project.

Why It Matters for the Exam

This concept appears frequently in questions about tailoring, project execution, and team collaboration. The PMI exam tests your understanding that models, methods, and artifacts are options—not mandatory prescriptions—and that project teams must deliberately choose which ones to use based on their project's unique context. Expect scenario-based questions asking which combination of models, methods, and artifacts best supports a given project situation.

Key Points to Remember (for the exam)

• Core Definition: Models, methods, and artifacts are the range of options available to produce deliverables, organize work, and enable communication and collaboration.
• Three Categories:
  • Models: Conceptual frameworks (e.g., situational leadership, communication models)
  • Methods: Systematic procedures or techniques (e.g., rolling wave planning, earned value management)
  • Artifacts: Tangible outputs or documents (e.g., project charter, risk register, accepted deliverables)
• Tailoring Connection: The selection of models, methods, and artifacts is part of the tailoring process—the deliberate adaptation of the project management approach to align with the project's environment and objectives.
• No Fixed Set: There is no prescribed list; teams choose based on project characteristics, development approach, and stakeholder needs.
• Integration with Performance Domains: Models, methods, and artifacts support all seven performance domains (Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk).
• Common Confusion: Confusing models (conceptual) with methods (procedural) or artifacts (tangible outputs)—each serves a different purpose in project management.

Typical PMI Exam Example

A project manager is starting a new software development project with a hybrid development approach. The team needs to organize work across multiple sprints while maintaining stakeholder visibility. Which combination of models, methods, and artifacts would best support this situation? The project manager should select an appropriate communication model, a rolling wave planning method, and create a project canvas artifact to align the team and stakeholders.

PMI Exam Traps

• Trap: Thinking models, methods, and artifacts are interchangeable terms.

  • Reality: Each has a distinct role—models provide frameworks, methods provide procedures, artifacts provide tangible documentation.

• Trap: Assuming all projects must use the same set of models, methods, and artifacts.

  • Reality: Selection is based on tailoring considerations—project environment, objectives, development approach, and constraints.

• Trap: Confusing "accepted deliverables" (an artifact) with "verified deliverables."

  • Reality: Accepted deliverables are validated against established criteria and approved by an appointed individual or group; verification is a different quality process.

• Trap: Believing models, methods, and artifacts are only relevant during planning.

  • Reality: They are used throughout the project life cycle to produce deliverables, organize work, and enable ongoing communication and collaboration.

Important PMI Connections

Quick Review Questions

1. What are the three categories of options that project teams can use to produce deliverables, organize work, and enable communication and collaboration?

2. How does the tailoring process influence the selection of models, methods, and artifacts for a project?

3. A project team is deciding whether to use a Gantt chart (artifact), a critical path method (method), or a communication model. Which category does each belong to, and why does this distinction matter?

4. In a scenario where a project has highly uncertain requirements, which type of development approach would likely influence the selection of methods and artifacts?

5. What is the difference between "accepted deliverables" and other types of project artifacts?

PMBOK v8 Reference

Section 4 - Models, Methods, and Artifacts (Introduction and Overview)