PMP prep exam free online course
Introduction &the environment in which
project operate - Objective and Constraints
We will complete Introduction & the environment in which project operate section. In the previous module (Introduction & the environment in which project operate - part 1) we took:
1- Project.
2- Operational Work.
3- Project Management.
4- Program.
5- Portfolio.
6- Project Management Office (PMO).
In this module we will take:
It also includes lessons learned and historical
information.
In this module we will take:
7- Objective.
8- Constraints.
Objectives & Management by objective (MBO).
Objectives is what need to be achieved as a result of
project.
Each project will have unique of objectives. For example, if
required to construct a bridge in a city the objectives can be as below: -
* Bridge will have 8 lanes in total.
* Bridge must carry at least 3.000.000 KG
* Must resist at
least 9 Richter Earth-Quakes.
It is only examples from objectives and sure construct
bridge project will have many other objectives.
Note- if objectives of a project cannot be met that project
can be consider as failed.
Important points about objectives.
- Projects are considered complete once objectives are met.
Therefore, project manager must monitor project objectives and if there are any
risk can cause of not meeting of any of objectives prevent and corrective
action should be taken accordingly.
- A reason for terminating a project before completing is that
the project objectives cannot be met.
- Meeting project objectives is under project manager’s
responsibility.
- Quality activities are for checking whether the project meet
its objectives.
- There are a trade-off between requirements & objectives.
Management by objectives (MBO).
Management by objectives is a management philosophy. This
philosophy ensure to complete a work, task, or activities by managing the
objectives that will bring you to the completion.
Management by objectives have 3 steps
Step-1: Establish clear & realistic objectives.
This is important because subjective objectives will not be
sufficient. For example, we will produce a very good car. This is an objective?
The answer is No because good, bad, fast, slow are all subjective. A very fast
car can be a slow car for another driver therefor objective must be
quantitative.
We will produce a car will reach to 100 KM/H in 10 Sec this
is an objective because we determine quantitative values.
Step-2: Periodically evaluate if objectives are met
Projects might take years to complete and sometimes several
resources can work on a package for long time therefor you need to check the
output of the work been to introduce whether it is meet the project objectives
otherwise your end product might be divide from what you desire to get it in a
beginning.
Step-3: Implement corrective action if there are problems.
You set the objectives and work start to complete the
project but there are problems in the middle of the work. You are seeing that
the objectives will not be met. You need to take a corrective action. This may
be quality of materials, person in your team, or a tool missing, ...etc.
whatever the reason is you need to find a problem and fix the root cause.
Constraints.
Constraint mean a
limitation or restriction by dictionary definition and it is similar to a
project management as well.
Project have
constraints and project manager should manage these constraints. There are 7
common constraints of projects, there are:
- Cost
- Scope
- Quality
- Customer satisfaction
- Risk
- Resources
- Time
Generally, there are
trade-off between these constraints. This mean improve positive aspect of a
constraint there will bring a negative aspect on one or more of other
constraints.
For example, in order
to reduce the delivery duration of the project or in order to deliver project
early the schedule time, you need to put extra resources to deliver the same
amount of work in a short time. This mean increasing cost. Or if you could not
put extra resources, you need to reduce scope to deliver the last work in a
short time scale.
As you see one impact
on one constraint might affect all the other constraints in the chain.
Therefore, if there is change one constraint you should evaluate its effect on
other constraints.
Organizational process assets.
Organizational process
assets are plans, processes, policies, procedures, and knowledge bases specific
to and used by the performing organization.
For Example, project
plan template, security policy, procurement procedure, and company knowledge
base are all categorize as an organizational process asset.
Organizational process
assets are input to most planning processes.
Corporate knowledge base
is for storing and retrieving information.
Enterprise Environmental Factors (EEF).
You will see
enterprise environmental factors are input to many processes in project
management.
Briefly, conditions
that are not under the control of the project team, that influence, constrain
or direct the project are categorize as EEF.
EEF are input to most
of planning processes.
Example of EEF:
- Organizational
culture, structure, and governance because as a project manager you can not
affect the management of your company or management hierarchy of your company.
However, approach of your management and hierarchy in a company directly affect
project management in a company.
- Government or
industry standards.
For example, if you
want to produce a health product this must be in comply with the standard of
world health organization and if you will market in USA it is needed to comply
and approved by FDA. Since this standard will impact your project scope there
are considered as EEF as well.
- Political climate.
Political climate is
very important for projects. For example, if your project will be executed in a
country that has embargo, most properly you will have procurement issues.
- Marketplace conditions.
Let consider that you
are working in a company which having an economic crisis and this effect the
renew view of your company directly. Respectively, your project will be
affected as well.