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:

Know it well enough for the exam? Questions on Organizational Process Assets (OPAs) are scenario-based, not definitional.

Practice it free

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.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Part of

PM Fundamentals & Frameworks

Study full domain →

Practice Organizational Process Assets (OPAs)

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.