Organizational Process Assets (OPAs): Value Delivery System Inputs

PMBOK v8 Definition

Organizational Process Assets (OPAs) are any artifact, practice, or knowledge from any or all of the performing organizations involved in the project that can be used to execute or govern the project. The OPAs also include the organization’s lessons learned from previous projects and historical information, as well as lessons from previous work carried out. Since OPAs are internal to the organization, the project team members may be able to update and add to the OPAs as necessary throughout the project.

Why It Matters for the Exam

OPAs appear as inputs to many project management processes across all Process Groups. The PMI exam frequently tests your ability to distinguish OPAs from Enterprise Environmental Factors (EEFs) and to recognize which artifacts are considered OPAs. Expect questions in process input identification, especially for Planning and Executing processes.

Key Points to Remember (for the exam)

• Definition Core: OPAs are internal to the organization—any artifact, practice, or knowledge used to execute or govern the project
• Main Input To: Many project management processes (across all Process Groups)
• Key Components: Completed schedules, risk data, earned value data, lessons learned from previous projects, historical information
• Updatable: Project team members can update and add to OPAs as necessary throughout the project
• Distinction from EEFs: OPAs are internal and can be changed by the team; EEFs are internal or external conditions that cannot be changed by the team
• Source: Previous projects and work carried out within the performing organization
• Common Confusion: Confusing OPAs with EEFs—remember OPAs are process assets (templates, policies, procedures, historical data) while EEFs are conditions (culture, infrastructure, market conditions)

Typical PMI Exam Example

A project manager is starting a new software development project. During the Planning phase, the project manager needs to reference the organization's standard project schedule template and historical risk data from three similar previous projects. Which input should the project manager use?

Answer: Organizational Process Assets (OPAs), because they include completed schedules, risk data, and historical information from previous projects.

PMI Exam Traps

• Trap: Confusing OPAs with Enterprise Environmental Factors (EEFs)

  • Reality: OPAs are internal artifacts the team can update; EEFs are conditions (internal or external) the team cannot change

• Trap: Thinking OPAs only come from the performing organization

  • Reality: OPAs come from any or all performing organizations involved in the project

• Trap: Assuming OPAs are static and cannot be modified

  • Reality: Project team members may update and add to OPAs as necessary throughout the project

• Trap: Believing OPAs are only inputs to Planning processes

  • Reality: OPAs are inputs to many project management processes across all Process Groups

Important PMI Connections

Quick Review Questions

1. A project team needs to use the organization's standard risk register template and historical earned value data from a previous project. Are these considered OPAs or EEFs?

2. During project execution, the team discovers a more efficient way to document project changes. Can they update the OPAs with this new practice?

3. A project manager is working on a project with three different partner organizations. From which organizations can OPAs be sourced?

4. True or False: OPAs are only used as inputs during the Planning Process Group.

5. What is the key difference between OPAs and EEFs regarding the project team's ability to modify them?

PMBOK v8 Reference

Section 2 – A System for Value Delivery (The Standard for Project Management, pages 20-22)