Professional Documents
Culture Documents
Project Management Mod 1
Project Management Mod 1
PE 309
MODULE 1
Dr. L N Pattanaik
Assoc. Prof.
Dept. of Prod. Engg.
BIT Mesra
Course Objectives:
This course enables the students to:
1 Comprehend the scope and types of projects
2 Identify the Project Life Cycle and project constraints
3 Construct organizational structure of project management
4 Realize environmental issues and social cost benefit analysis of projects
5 Apply project scheduling tools (PERT and CPM)
Course Outcomes:
After the completion of this course, students will able to:
• CO1 Recognise the project morphology, organizational structure and elements of project
• CO2 Incorporate the importance environmental issues in projects
• CO3 Handle real-life projects as in various organizations
• CO4 Solve complex scheduling problems in project management using PERT/CPM
• CO5 Prepare project report and budget planning
SYLLABUS
Module 1: Definitions and basic terms [7 classes]
• Definition and types of project, Turnkey projects, Scope of project and
creep, Project life cycle, Project constraints
Project Engineering Vs Project Management
Global projects
• Space Exploration
• Environment protection
• Global Warming
Project Examples
•
Scope of a Project
• Project scope is the part of project planning that involves determining
and documenting a list of specific project goals, deliverables, tasks,
costs and deadlines.
• The documentation of a project's scope, which is called a scope
statement or terms of reference, explains the boundaries of the
project, establishes responsibilities for each team member and sets
up procedures for how completed work will be verified and approved.
• Large projects naturally tend to change as they progress. If a project
has been effectively "scoped" at the beginning, then managing these
changes will be easier. When documenting a project's scope,
stakeholders should be as specific as possible to avoid scope creep, a
situation in which one or more parts of a project end up requiring
more work, time or effort because of poor planning or
miscommunication.
Real world example of scope creep (the Killer of Projects)
• When a project fails to be properly defined, planned or documented, something
called scope creep or requirement creep can occur. This should be avoided if
possible as it can lead to uncontrolled growth of the project.
When the schedule of a project needs to decrease, the project might need to
increase the budget because more resources are needed to do the same work
in less time. If the budget cannot be increased (the donor doesn’t approve the
increase), then the scope might need to reduce because the resources
available will not be sufficient to complete all the planned work in less time.
When the project scope increases, there is a need for more time or more
resources (budget) to complete the additional work. When the project adds
more work than the originally budgeted it is important that before the new
work is started, there is an approval from the donor for additional funds,
otherwise the project will end up with a budget shortfall that could have an
impact on the expectation of the beneficiaries.
Quality is at the center of the project triangle because it affects every
side of the triangle, any changes made to any side of the triangle are
likely to affect the quality. Quality is not a factor of the triangle; it is a
result of what you do with the schedule, budget, and scope.
For example, the project may find additional time in the schedule that
can allow staff the time to increase the quality of the objectives
without necessarily increasing the scope. On the other hand, a need to
cut activities to meet the budget might result in a decreased scope,
which reduces the opportunities to achieve an acceptable level of
quality; therefore, lower quality results from the need of cutting costs
and reduce planned activities.
Scope, schedule and budget are the three essential elements of any
project. To succeed as a project manager, one has to know about how
all four of these constraints apply to projects.
Benefits and Risk as constraints (new theory)
• The last two elements of the six-constraint model are the newest and
least-familiar ones, and could be considered controversial – except
that they are both already present in projects. We are not creating
them – we are just bringing them to the forefront and demonstrating
how they interact with the “classic” constraints (time, cost, scope,
and quality). When these two new constraints – benefits and risk –
are not considered, they are likely to be neglected and produce a
negative impact on the project and the organization. We will examine
those potential consequences as we discuss each of them.
Benefits as constraint
• Benefits represent the value the project is expected to deliver to the
organization.
• As the project has deliverables that it produces, the benefits
represent the value that those items are expected to have for the
organization (in financial or other terms).
• A clear justification, with measurable, agreed benefits that are
expected to result from the project's outputs. If there is no clear
justification, then the project should not be started, and if the
justification disappears – or is reduced below an agreed-upon limit –
the project should be stopped.
• That “limit” will become a constraint.
Risk as constraint
• Risk on a project needs to be addressed and managed.
• In any project there may be a level of risk that the stakeholders not willing
to live with or “tolerate.” That is known as risk tolerance.
• Its simplest and most common expression is in examining the probability of
significant risks occurring, their potential impact on the project if they do
occur, and the degree of willingness to live with those potential
consequences.
• An Agreement on the level of risk the sponsor/ stakeholders/ Project Board
are willing to live with in the course of the project (their risk tolerance).
• If the project manager cannot control (mitigate/ transfer, etc.) major risks,
then the sponsor/ stakeholders/ Project Board need to decide if they are
willing to live with the greater risk exposure, or want the project to close
down
End of Module I