Enterprise Environmental Factors and Organisational Process Assets
It’s time to look at the environment in which projects operate.
The environment can really change the way you need to manage a project, and this is why it is included in the PMBOK Guide. The way it is outlined is through two things: Enterprise Environmental Factors (EEFs) or the overall environmental factors involved, and Organizational Process Assets which will help us to operate within the project environment that we’re delivering in.
These are the two main things that you’ll see come up time and time again in each of the project management processes as we go through the PMBOK guide.
Organizational process assets or OPAs could be processes, procedures, policies or a corporate knowledge base. Enterprise environmental factors or EEFs are enterprise conditions, and they’re usually not under the control of the project team (which can make things a little bit difficult) but they still influence, constrain or direct the project.
Let’s have a look at what some of the Internal EEFs are. We’ve got organizational culture, any structure and governance that’s in place, we’ve got the geographic distribution of facilities and resources (are they all in the one place or across multiple states or countries?). We’ve got the actual physical infrastructure, and sometimes the I.T. infrastructure involved. We’ve got the information technology software that we’re using, the resource availability (how available are the resources that we’re needing to help deliver these projects), and of course the capability of all these people (have they delivered projects before? Are they familiar with the process?)
Many different things will influence the internal EEFs. To complicate things there are external EEFs as well.
We’ve got government or industry standards, we’ve got social and cultural influences, marketplace conditions, legal restrictions, cost constraints and financial considerations (do we actually have the money to to do what we need to do?) and physical environmental elements (are we in the right place physically to be able to do these things?). These are just a few examples of enterprise environmental factors or EEFs that will influence and change how you need to deliver your project.
But that’s not the only thing we have to consider. The other side of the coin is our OPAs, our Organizational Process Assets. These are the plans, the processes, policies, procedures, all of these documents and knowledge bases, things that are used by the performing organization that you’re working with and usually delivering into. OPAs will influence the management of the project because we’ll have things like specific organizational standards. You might have certain product or project life cycles that are already used in that organization (such as Agile or Waterfall). You might have pre-approved supplier lists lists or contractual agreements already in place that you need to abide by.
There are knowledge repositories as well – so you might have configuration management knowledge repositories, containing versions of things, of your baselines for your scope or maybe of the cost of the project. Historical information, lessons learned, data repositories for measuring your benefits, project files from previous projects. All of these things will impact your OPAs and your project.
As a project manager you will need to find all this out when you’re delivering a project, so you can make sure that you work within these Organizational Process Assets and ways of working that are already in place.
– David McLachlan