Resources, deliverables, costs. These are just some elements you need to include in a project plan. You also need to consider the external and internal factors affecting project management as well.

What about areas such as decision-making, internal skills, market conditions, or existing supplier contracts? Have you considered quality standards, codes of conduct, and lessons from past projects?

These areas are known as enterprise environmental factors (EEFs) and Organizational Process Assets (OPAs).

EEFs and OPAs create the working environment for your project, influencing elements such as project approval, software usage, and risk management.

Generally, EEFs are outside the control of the project team and can help or hinder your project.

OPAs are internal, specific to an organization, and are designed to support project teams.

In this article, you’ll learn more about EEFs and OPAs, including examples and how these factors impact on your project.

What Are Enterprise Environmental Factors in Project Management (EEFs)?

According to the Project Management Body of Knowledge (PMBOK), EEFs are internal or external conditions that can impact the project but are not within the control of the team.

As EEFs describe the circumstances in which your team will work, it’s important to investigate these factors during the planning phase.

EEFs are categorized as either internal or external to an organization.

Examples of Internal Factors Affecting Project Management

• Organizational culture, for example, vision, mission, and values.
• Existing project management software.
• Product standards.
• Quality standards.
• Resource availability, including physical infrastructure and the location of resources.
• Risk tolerance.
• Project stakeholders.
• Organizational stakeholders.

Examples of External Factors Affecting Project Management

• Market conditions
• Consumer trends
• Industry or government regulations
• Financial considerations, such as trade, taxation, and inflation.

EEFs determine the types of projects undertaken within an organization and your options for managing projects, for example, approaches to risk, leadership, and decision-making.

Although these factors may be outside of your control, it’s important to reflect on EEFs when planning your next project. Accommodating restrictions such as software or strict quality control processes is easier before any work starts.

A useful framework for assessing external factors is PESTEL.  The framework is based on six environmental types:

• Political – trade, taxation, stability.
• Economic – customer demands and trends, inflation, interest rates.
• Social – customer demographics and expectations.
• Technological – new services and products; advancements such as automation.
• Environmental – corporate responsibility, environmental restrictions.
• Legal – health and safety, employee and consumer rights, regional laws.

What Are Organizational Process Assets (OPAs)?

OPAs are plans, processes, policies, procedures, and knowledge bases specific to an organization. Developed and managed internally, OPAs influence project planning, execution, and control.

Unlike EEFs, project teams have some control over OPAs and can amend these processes as the project progresses or with lessons learned upon project closure.

OPAs help organizations to improve their processes, share best practices, and develop project management skills.

OPAs can be divided into two groups:

• Processes, Policies, and Procedures
• Knowledge bases

Processes, Policies, and Procedures

The Project Management Office is often responsible for creating, sharing, and updating processes, policies, and procedures.

They are documented processes and procedures that an organization follows to complete its work and include guidelines for how projects are initiated, planned, executed, monitored and controlled, and closed.

These can include:

• Standardized templates such as project management plans, communication plans, and lessons learned.
• HR policies
• Procurement policies
• Project management methods
• Preapproved supplier and contractor lists
• Change management processes
• Issue Management procedures
• Project Closure guidelines
• Finacial control procedures
• Risk registers.

Knowledge bases

The value of internal knowledge bases for successful projects should not be underestimated. In such repositories, you’ll find a trove of information about past projects, decision-making, the role of stakeholders, and so on.

These resources “will help you understand the environment you will have to master”.

Knowledge bases are typically used to store:

• Information about software and hardware within the organization
• Financial information such as budgets and cost overruns on past projects.
• Files from previous projects including lessons learned, risk management activities, scope, schedule, and project closure. 

It’s also good practice to check on metrics of success and reporting mechanisms on previous projects. This data indicates what is important to stakeholders and should be included in your project site or reports.

Manage Enterprise Environmental Factors and Organizational Process Assets with Microsoft 365

It would be virtually impossible to manage and influence every enterprise environmental factor affecting your project management, especially the external factors. Regardless, it is important to be aware of them so you can have mitigation and contingency plans ready to go.

Your organizational process assets are a valuable resource for project managers as they can provide a baseline of best practices, help streamline project management processes, and improve project outcomes.

Better yet, leveraging the right platform like Microsoft 365 means you can bake them right into your project management software.

Microsoft 365 offers several tools that can be used to manage organizational process assets (OPAs) and guide project execution.

Create Project Management Templates Using Power Apps

Power Apps is a low-code platform that allows project teams to create custom applications to manage project-related data and workflows.

It can be used to support OPAs by developing apps and project templates that support the way your organization has decided to manage projects.

BrightWork 365 ships with several project management templates out-of-the-box (with many more to come!), all leveraging Power Apps to support predefined project management processes.

The Power App-based project management templates are highly configurable to match your project workflows exactly, and can even be pre-populated with tasks, stages, and milestones for various types of projects.

By giving your organization templates with which to manage projects, you give project teams a set of rail tracks to follow and manage project the right way.

Manage Project Documentation with SharePoint Online

SharePoint Online is a web-based collaborative platform that is used to store and manage project documents and deliverables in Microsoft 365.

Often OPAs will require certain documents to be submitted or deliverables to be completed before a project can move on to the next stage or be closed

In BrightWork 365, anywhere you are storing documents you are using your SharePoint Online in your Microsoft 365 secure tenant. All BrightWork 365 project sites can have SharePoint Online library built in so any required documentation is associated with the relevant project.

SharePoint Online provides document management, version control, and access control features that allow project teams to store and share project documentation.

Leverage Microsoft Teams for Collaboration and Knowledge Sharing

Microsoft Teams is a collaboration platform that allows project teams to communicate, share files, and collaborate on project-related tasks.

Organizations can use Teams to leverage the experience and knowledge of their employees and continuously improve their project management practices.

Creating a Teams or channel for your project provides a searchable knowledge base where you can store and share project-related information and OPAs. For example, you could add a project wiki that includes lessons learned, best practices, and other information that can be used to improve project outcomes.

Editor’s Note: This post was originally published in March 2020 and has been updated for freshness, accuracy, and comprehensiveness.