Organizational Process Assets (OPAs) for the PMP Exam

Organizational Process Assets: Your Project's Built-In Toolkit

If enterprise environmental factors are the conditions you can't control, organizational process assets (OPAs) are the accumulated wisdom and tools your organization hands you. OPAs include everything from templates and checklists to historical data and lessons learned. They are inputs to almost every planning process in the PMBOK Guide, and the PMP exam tests whether you understand how to use them effectively.

Two Categories of OPAs

PMI divides OPAs into two broad categories. Understanding this distinction helps you answer PMP questions quickly and accurately.

Processes, Policies, and Procedures

These are the organizational rules and standard approaches for getting work done:

• Project management methodologies and standards
• Change control procedures
• Financial controls and approval processes
• Communication templates and reporting requirements
• Issue and defect management procedures
• Risk management policies and categories
• Quality policies and audit procedures
• Procurement policies and approved vendor lists

These OPAs provide guardrails. They tell the project manager how the organization expects work to be done. You can typically update and improve them as part of lessons learned, but you generally follow them during the project.

Organizational Knowledge Repositories

These are the accumulated data and knowledge from past projects:

• Historical project data (schedules, budgets, performance metrics)
• Lessons learned databases
• Configuration management knowledge bases
• Financial databases (labor rates, cost estimates, budget data)
• Issue and defect databases from previous projects
• Project files from previous projects

Knowledge repositories are especially valuable during planning — they let you base estimates on actual data rather than guesses.

OPAs in Practice: How They Shape Project Work

Consider a project manager starting a new software development project. The organization's OPAs might provide:

1. A standard project charter template (so you don't start from scratch)
2. Estimation guidelines based on similar past projects
3. A risk register template pre-populated with common risks for software projects
4. Lessons learned from the last three software projects (including pitfalls to avoid)
5. Standard procurement procedures for hiring contractors

Using OPAs effectively means not reinventing the wheel. The PMP exam rewards candidates who leverage existing organizational knowledge rather than treating every project as if it's the first one the organization has ever run.

The Lessons Learned Connection

Lessons learned deserve special attention because they flow in both directions. At the start of a project, you consume lessons learned from past projects (they're OPAs). Throughout and at the end of your project, you create new lessons learned that become OPAs for future projects.

The PMP exam frequently tests this cycle. A common question pattern presents a project that encounters a problem already documented in the lessons learned database — the correct answer involves consulting that database before attempting to solve the problem from scratch.

Key Exam Distinctions

Remember these points for exam day:

• OPAs are things you can use and update; EEFs are conditions you work within
• OPAs are always internal to the organization (there's no such thing as an external OPA)
• Templates, historical data, and lessons learned are classic OPA examples
• When a question mentions "past project data" or "organizational standards," think OPAs

Test your understanding with PMPprep's domain-specific practice questions. Filtering for Business Environment questions will help you encounter OPA scenarios in the context the exam uses them.