1

Lec-2

Presented by
Rehan Asad
BS, MS, PhD Scholar, PMP®
 2

Agenda

• Organizational Process Assets (OPAs)

• Enterprise Environmental Factors (EEFs)
• Stakeholders
• Project team
• Project life cycles
 3

Organizational Process Assets (OPAs)

These are the documental assets that are available in the organization.
That can be useful in Planning and execution of the project.

OPAs can be grouped in two categories

1. Procedures and Processes

2. Knowledge base
 4

Organizational Process Assets (OPAs)

Examples of processes and procedures :

• HR policies; e.g medical policies, compensation policies
• Templets and forms (risk, schedule, WBS, others)
• Change control procedures
• Financial control procedures
• Issues and defect handling procedures
• Communication procedures, risk control procedures
• Work instructions, evaluation criteria, performance measurement criteria
• Audits, project evaluations, Project validations, acceptance criteria
 5

Organizational Process Assets (OPAs)

Corporate knowledge database examples:

• Historical information of projects handled by the organization earlier

• Lesson learned from previous projects
• Issues and defect management database
• Project files from previous projects
• Configuration management knowledge base
• Financial database
 6

Enterprise Environmental Factors (EEFs)

These are conditions that are not under the control of project team ,BUT
can have an effect on the project.

These conditions can help in the PM while developing the plan and during
other stages of the project .

Generally EEFs are of two types:

1. Internal, that are within the organization
2. External, that are outside the organization
 7

Enterprise Environmental Factors (EEFs)

Internal EEFs
(Related to the organization)
• Organizational culture, structure
• Infrastructure facilities inside the company
• HR administration
• Company work authorization system
• Stakeholder risk tolerances
• Project management information systems
used by the company
External EEFs
(Related to the place of project)
• Market place conditions
• Government / industry standards
• Political situation
• Human resources availability
• Communications systems
• Commercial databases availability
• General security
• Infrastructure
 8

Project Stakeholders:

• Stakeholder is an individual, group, or organization who may affect, be

affected by, or perceive itself to be affected by a decision, activity or
outcome of a project.

• Stakeholder can be directly or indirectly connected to the project

 9

Project Stakeholders:

• Sponsor
Sponsors provides the finance for the project. They also initiate projects
• Customer or user
Customers are user can be internal or external they use the outcome of the project product service
or result.
• Sellers/business partners
External stakeholders/companies such as vendors, contractors, suppliers.
They could be user of the project outcome.
• Functional managers
They give functional support to the project in different areas. e.g HR, finance, accounts, IT
• Others – Financial institutions, consultants, government agencies
 10

Project Team:

• The project team includes the project manager and the group of the
individuals who act together in performing the work of the project to
achieve its objectives.

• Team includes project manager, project staff, project management staff

or other team members who are connected with the project
 11

Project Team:

• Project management staff:

Carry out scheduling, budgeting, controlling, communication, administrative support for the project
• Project staff :
Carry out the work related to the project activities
• Supporting experts:
Testing, financial management, logistics, others
• User or customer representatives:
Give input to project design, accept deliverables
• Sellers:
Vendors, suppliers, contractors, external companies with agreements
• Business partner/members:
 12

Project Life cycles:

1. Predictive or Plan driven life cycle

2. Iterative and Incremental life cycles
3. Adaptive life cycles
 13

Project Life cycles:

1. Predictive or plan driven life cycle

• In this project lifecycle the project scope is known at the start of the
project and time and cost to deliver the scope is determine early in the
life cycle of the project .

• This is also called the “waterfall” or the “traditional approach” of

project management
 14

Project Life cycles:

2. Iterative and Incremental life cycles

In this project scope is generally finalized early in the project lifecycle

however time and cost estimates are not firmed up and they can be
modified as team’s understanding of the project increases.

Hence the work may have to be done in incremental cycles depending on

the understanding of the scope
 15

Project Life cycles:

3. Adaptive life cycles

(Also known as change driven or agile methods)

In this, the idea is to be flexible and accept changes in the scope as the
project goes ahead these changes in scope are done with involvement of
business owner or customer for whom the project is being done.

Project work is done in iteration, based on the scope

This approach is used mostly in software development project

 16

Thank
you