Skip to content
PMPCAPM

Organizational Process Assets (OPAs)

Organizational Process Assets (OPAs) are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization.

Share:

Explanation

OPAs are the accumulated knowledge and resources of the organization that can be drawn upon to plan and manage projects. They fall into two categories: processes, policies, and procedures (things the organization has established for how work should be done) and organizational knowledge bases (accumulated information from past projects and operations).

Examples of processes, policies, and procedures include standardized project templates, change control procedures, financial controls, communication requirements, issue and defect management procedures, and risk management policies. Examples of knowledge bases include lessons learned repositories, historical project data, configuration management databases, financial databases, and process measurement data.

OPAs are a critical input to many project management processes. Unlike EEFs, OPAs are within the organization's ability to update and improve. In fact, projects contribute to OPAs when they capture lessons learned, update templates, or add historical performance data. This creates a virtuous cycle: good OPAs help future projects succeed, and well-managed projects improve the OPAs for the organization.

Key Points

  • Two categories: processes/policies/procedures and knowledge bases
  • Accumulated from past projects and organizational experience
  • Can be used by the project team AND updated by the project team
  • Include templates, lessons learned, historical data, and policies

Exam Tip

The key distinction: OPAs are assets you USE and UPDATE; EEFs are conditions you WORK WITHIN. If the exam mentions templates, historical data, or lessons learned, it is referring to OPAs.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Predictive Life Cycle (Waterfall)

A predictive life cycle is a plan-driven approach where the project scope, schedule, and cost are determined early and changes are carefully managed.

Subsidiary Plans

Subsidiary plans are the individual management plans that are components of the overall project management plan, each addressing a specific Knowledge Area or management function.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Part of

PM Fundamentals & Frameworks

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.