Basics of Project Management
Basics of Project Management
Basics of Project Management
A project is a non-recurring task having a definable beginning and end, with a definite mission and
has a set objectives and achievements.
According to PMI A guide to the project management body of knowledge (PMBOK guide)
Types of Projects
Personal Project
Writing a Report/Book.
Business/Organisational Project
National Projects
Swatch Bharat Abhiyan
E-Governance/Digital India
Global Projects
Elimination of Polio
Characteristics of Projects
1. Change
2. Fixed set of objectives
5. Temporary
6. Cross-functional/Teamwork
7. Unique
8. Life cycle
9. Made to order
8. Single entity
9. Multi-skilled staff
10. Subcontracting
11. Risk and uncertainty
Operations
Operations are ongoing execution of activities that produce same output or provide a repetitive
service.
Both are subjected to constraints like resources, schedule, risk and etc.
Stakeholders
Stakeholder is a person, group of individuals or organisations, who is positively or
negatively impacted by the project and/or anyone who can exert influence over the
projects objectives and results.
Generally in any project stakeholders are as below.
(a) Project Manager
(b) Sponsor
(c) User/Customer
(d) Sellers or Business Partners
(e) Project Team
(f) Departmental Managers
(g) Board of Directors
(h) Project Management Office
Project Constraints
Constraints are limiting factors or holding back elements that decide upon the boundaries of
project.
(i) Scope
(ii) Quality
(iii) Schedule
(iv) Budget
(v) Resources
(vi) Risk
Good communication and Co-ordination between projects. Reduce conflict between projects
Better resource utilization
Portfolio
Note that in program management only related projects were managed whereas in portfolio
related and non-related projects are managed.
Benefits of Portfolio
Better allocation and utilization of resources between projects and programs. Extending
constant support to projects or programs.
Project Manager
A project manager is an individual with authority, accountability and responsibility for managing a
project to achieve specific objectives.
Characteristics of Good Project Manager
1. Good technical skills
2. Leadership skills
3. Resource management
4. Human Resource Management
5. Communication skill
6. Negotiation and Influencing skill
7. Conflict Management skill
8. Marketing, Contracting, customer relationship skill
9. Budgeting & Costing skill
10. Scheduling and time management skill
11. Team building
12. Motivation skills
13. Decision making skills
14. Political and Cultural awareness
15. Trust building.
Organisational Structure
Organisational structure is the hierarchy of people and its function.
An organizational structure defines how activities such as task allocation, coordination and
supervision are directed towards the achievement of Organisational aim.
It enables the co-ordination and implementation of project activities by creating an environment
which felicitates interactions among the team members with a minimum amount of conflict and
friction.
Generally position of project manager does not exist, whereas if there is a project manager their
role will be limited and requires approvals from functional managers.
Sometimes Project manager may have title of Project Co-Coordinator
Advantages
Employers are very skilled and efficient because they are experienced in same work.
There is no duplication of work as roles and responsibility of each employee is fixed.
Clear cut hierarchy i.e. each employee reports to his functional manager, which results in better
communication and co-operation.
Disadvantages
Employees might feel bored due to the monotonous, repeated type of work and may become
lazy.
Cost of high skilled employee is higher.
Departments develop a self-centered mentality i.e. functional manager only pays attention to
his department and dont care about other departments.
Each department will start behaving like a small company with its own culture and management
style.
Project manager has little or no authority.
Carrier path is not clearly defined for project manager, sometime they may be on part time pay
roles.
II. Projectised Organisation
In projectised organization structure, project manager has full authority to assign persons
assigned to the project.
Here either there will be no functional manager, or if exists, he will have very limited role and
authority.
Projectised organisation are only interested in project work which they get from external clients.
Generally they have some small departments such as Admin, Accounting, and Human
Resource to support the project Management activities.
Advantages
As all the team members directly report to only one project manager, there is a clear line of
authority. This reduces conflict and enables decision making faster and flexible.
Team members become versatile and flexible due to experience in different Kinds of project.
Single reporting system creates a strong and effective communication within the project team.
Disadvantages
As project manager has full authority and power over his team, he can become arrogant and
dominating.
If any organisation has multiple projects, then there can be poor communications among them,
which can result in duplication of resources.
Employees are less loyal to the organization because there is a sense of insecurity among
them i.e. once the project is complete; they feel that they may lose their jobs.
Advantages
Highly skilled resources can be shared between functional units and departments.
Matrix structure is more dynamic than functional structure because it allows employees to
communicate more readily across their functional departments.
It creates a good working and co-operative environment which helps in integrating the
organisation.
Employees can learn and widen their skills and knowledge by participating in different kind of
projects.
As there is a sense of job security, employees tend to be loyal to the organisation and perform
well, and therefore efficiency increases.
Disadvantages
Employees have to report to two bosses, which may create confusion and conflict.
A conflict might arise between the project manager and the functional manager for the share of
authority and power.
If priorities are not clearly defined, employees may have confusion between their role and
responsibility, especially when they are assigned a task which is different from what they were
doing.
For a rare resource their might be a competition to use it, which may cause chaos within the
work place and may affect the operation.
Project manager or organizations can divide projects into phases to provide better management
control over the projects.
It also helps in identifying deviations and thus helps in decision making with regard to continuation
or termination of the project.
Then project is split up into phases which can be either sequential or overlapping.
Requirements are defined early and not expected to change.
This life cycle is also known as Change-Driven life cycle or Agile life cycle.
In Adaptive life cycle is also, sequential or overlapping, same as predictive.
At the end of each iteration, work for the product is reviewed by the customer, and feedback from
the customer is used to define the detailed scope for next iteration
This life cycle is used for projects where rapid changes are expected and it is not possible to define
scope in the start.
Adaptive life cycle is generally used in IT industry.
2. Project Management and Knowledge Areas
Project Management is accomplished by the appropriate application and integration of 47
processes.
Each process needs three essential elements i.e. Input, Output, Tools and Techniques.
Inputs are essential ingredients for start of any particular process.
Outputs are outcome or result of any process.
Tools and Techniques are methodology and actions required for the transformation of
input of any process into Output.
These processes are organized of classified into 5 process groups and 10 knowledge
areas.
t
Ac
Pl
an
Ch
ec
Do
k
Technical Feasibility
Factors Considered in Technical Analysis
a. Selection of Locations
b. Government incentive considerations
c. Technology selection and sourcing
d. Capacity planning
e. Raw material planning
f. Utility (water, power, waste, etc)planning
(b) Government Incentives:- SEZ, EOU(Export Oriented Units),EPU (Export Processing Units).
Market Feasibility
1. Jury Opinion
! Jury opinion is a method of combining views of several executives regarding a forecast.
! The general practice is to bring together top executives from various fields of management, which is
finance, human resources, marketing, purchasing and production.
! They provide information experiences and opinions to project planning.
! Jury opinion is simple and commonly used as it is less time-consuming.
2. Delphi Technique
Delphi method is a group process and aims at achieving a consensus of the members
! Herein experts in the field of marketing research and demand forecasting are engaged in
analyzing economic conditionscarrying out sample surveys of market conducting opinion polls
! Demand forecast is worked out in following steps:
1. Coordinator sends out a set of questions in writing to all the experts co-opted on the panel who
are requested to write back a brief prediction.
2. Written predictions of experts are collated, edited and summarized
3. Based on the summary, Coordinator designs a new set of questions and gives them to the same
experts who answer back again in writing.
4. Coordinator repeats the process of collating, editing and summarizing the responses.
5. Steps 3 and 4 are repeated by the Coordinator to experts with diverse backgrounds until
consensus is reached.
! Direct interaction among experts is avoided and their identity is also not disclosed.
! Procedure also avoids inter-personnel conflicts nor are strong-willed experts able to dominate the
group.
! This method is also used for technology forecasting
(b) Quantitative Techniques
Example
Calculate the forecast (using simple moving average method) for 2010 if demand were 32,36,
40,35,32,35 and 45, respectively, in each corresponding year from 2003 to 2009.
Table
Year Demand 4-year moving average forecast
2006 32
2007 36
2008 40
2009 35
2010 32 35.75
2011 35 35.75
2012 45 35.50
Sol. The forecast for 2013 is the arithmetic mean of demand of last four years, viz. 2009 to 2012.
Forecast for 2013 is 36.75
Example : Determine the forecast for 2010 and 2013 using least square method for the data given below:
Year 2005 2006 2007 2008 2009
Demand 35 42 45 51 56
Solution :
Least square method
Table
Year Demand(D) Year (T) T2 TD
2005 35 -2 4 -70
2006 42 -1 1 -42
2007 45 0 0 0
2008 51 1 1 51
2009 56 2 4 112
Total 229 10 51
Equation of line is D = a + bT
D/N
a = !
DT/T 2
b = !
a = 45.8 ; b = 5.1
! Forecast for 2010 is 61.1 (using T = 3). = D = 45.8 + 3 5.1 = 61.1
! Similarly, forecast for 2013 is 76.4 (using T = 6). D = 45.8 + 6 5.1 = 76.4
! In the above example, the middle year is assigned a value of 0;
! If the number of data available is even, the two middle terms can be assigned value of -1 and +1,
respectively, with a common difference of 2.
Financial Feasibility
! Importance and Steps of Financial Feasibility
! Financial feasibility is the process of identifying the overall investment outlay, determining expected
rate of returns and evaluating project financially.
! Financial feasibility is crucial for any organization as:
! It influences the firms growth in long term
! It affects risk of the firm into consideration
! It involves huge quantum of funds generally
Example: Mr. Sharma is investing Rs. 300 Lacs in a project and he is projecting cash flow of Rs. 50 lacs
every year, calculate the payback period for the project.
Solution :
Payback Period (PB) = 300/50 = 6 years.
Payback period can also be thought of as time at which break-even takes place
Social Costs
If any activity leads to depletion of a certain resource, it is a social cost.
Social Benefits
It is not that projects are only causing cost to society; they are also providing benefits to society.
(i) Improve environment
(ii) Products and services provided
(iii) Employment creation
(iv) Taxes
(v) Indirect employmentEarning foreign exchange
(vi) Hospital and educational facility
(vii) Development of backward area
4. Risk Analysis
! Risk is made up of two parts: the probability of something going wrong, and the negative
consequences if it does.
! Risk Analysis is a process that helps you identify and manage potential problems that could
undermine key business initiatives or projects.
Types of Risks
1. Operational risk
2. Market risk
3. Economic risk
4. Financial risk
5. Technological risk
6. Commercial risk
7. Quality risk
8. Legal or regulatory risk
9. International risk
1. Identification of Risk
2. Determining causes of risk and
constraints involved
3. Quantifying the risk
(a) Sensitivity analysis
(b) Earned Monetary Value (EMV)
(c) Modeling and simulation
(d) Risk matrix analysis
4. Develop the Alternatives
(a) Mitigation
(b) Sharing
(c) Out sourcing
(d) Diversification
(e) Abandonment
(f) Retention
(g) Contingency funding
(h) Time buffers
5. Selection of best alternative
6. Creation of risk management Plan
7. Implementation of risk management Plan
8. Review of risk management Plan
5. Project Planning
The purpose of the Project Planning process is to kickoff a new project and establishes an accurate plan
and schedule.
4. Project Scheduling
Steps in project scheduling
(a) Defining the Activities
(b) Sequencing the Activities
(c) Estimating the Resources Required
(d) Estimating the Time Required
(e) Developing the Schedule
Pert CPM
(1) Network diagram is event oriented. (1) Network diagram is activity oriented.
(2) It uses probabilistic approach and is suitable for (2) It uses Deterministic approach and is
research & development and non repetitive project. suitable for repetitive type of project.
(3) 3 time estimates are given for completion of an (3) Single time estimate is given for each
activity. activity.
(4) Follows distribution. (4) Follows Normal distribution.
(5) Cost of project is directly proportional time and (5) Cost model has to be developed
hence to minimize the project cost the project using which min. cost of the project is
completion time is minimized. found.
(6) Critical events are identified by using the concept of (6) Critical activities are identified by
slack. using concept of float.
(7) Critical path will be path joining the critical events. (7) Critical path will be the path joining all
the critical activities.
Indirect Cost
! Indirect cost of a project are those expenses which can not be associated or assinged to any
individual activity of the project,
! Indirect cost include overhead charges, for example : establishment charges, insurance charges,
expenditure for maintenance of services during operations.
! Indirect cost also include loss in profit or liquidity damages or penalty for delay in project complication,
which is known as Outage Loss.
Direct Cost
Direct cost of a project are those expenses which are directly chargeable and can be identified by
activities eg. cost of material, machine, labour etc.
Crashing
The process of reduction of total project duration along the longest path (time wise) of the network i.e.
along the critical path to obtain the optimum project cost and optimum duration is called as crashing.
Resource Allocation
! A resource is a physical variable quantity such as material, labour, equipment, time or space, which
are required for carrying out a project.
! During planning stage, we generally assume that sufficient resources are allocated to perform the
various activities and complete the project.
! But in reality resources are always limited, and this limitation of resources can significantly affect the
start, performance and completion of activities on scheduled time.
! Therefore, various activities of project should be scheduled in such a way that the demand for various
resources is more or less uniform during the project duration.
Resource smoothing
In resource smoothing the total project duration is not changed but the activities having floats are
rescheduled such that a uniform demand for the resources is achieved.
Resource Levelling
In resource levelling the activities are rescheduled such that maximum or peak demand of the
resource does not exceed the availability of resources.
6. Project Monitoring & Control
Project Monitoring is collecting, recording, and reporting information concerning project performance that
project manager and others wish to know.
Project control is the process that uses data collected during project monitoring and to bring actual
performance to planned performance.
PLAN
Specifications
Project Schedule
Project budget
ACTION Resource plan
Correct Vendor contracts MONITOR
deviations Record status
from plan Report progress
COMPARE Report cost
RE-PLAN as
Actual status
necessary
against plan
-Schedule
-Cost
!
What Do We Monitor?
1. Scope
2. Time:
3. Cost
4. Quality/Technical Performance
5. Risk
6. Team
When do we monitor?
Ans: @ End of the project, Continuously & Regularly
1. S-Curve
! S-curves are an important project management tool it allow the progress of a project to be tracked
visually over time, and form a historical record of what has happened to date.
! Analyses of S-curves allow project managers to quickly identify project growth, slippage, and
potential problems that could adversely impact the project if no remedial action is taken.
! Graphic display of cumulative costs, labor hours, or other quantities, plotted against time.
! The name derives from the S-like shape of the curve (flatter at the beginning and end, steeper in
the middle) produced on a project that starts slowly, accelerates, and then tails off.
(a) Determining Growth using S Curve
!
Comparison of the Baseline and Target S-curves quickly reveals if the project has grown (Target S-curve
finishes above Baseline S-curve) or contracted (Target S-curve finishes below Baseline S-curve) in scope.
SLIPPAGE
Man House /Costs
! Slippage is defined as: The amount of time a task has been delayed from its original baseline
schedule.
! The slippage is the difference between the scheduled start or finish date for a task and the baseline
start or finish date.
! If the resources are fixed, then the duration of the project will increase (finish later) or decrease
(finish earlier), possibly leading to the need to submit an extension of time claim.
(c) Determining Progress using S Curve
Comparison of the Target S-curve and Actual S-curve reveals the progress of the project over time. In
most cases, the Actual S-curve will sit below the Target S-curve for the majority of the .
Basic Terms
EVM consists of the following three basic elements:
Today
Cost
Actual Cost: What has
n ed
been actually spent to Plan
this point in time
Planned Value: What the
plan called for on the tasks
planned to be completed
by this date
al Earned Value: Value (cost)
ctu
A of what has been
ned accomplished to date,
Ear per the base plan
! Time
The sum of budgets for all work packages scheduled to be accomplished within a given time period.
(b) Earned Value (EV) or Budgeted Cost of Work Performed (BCWP)
The budgeted cost of work actually performed in a given period or the budgeted level of effort actually
expended.
(d) Cost Variance (CV) = Earned Value (EV) Actual Cost (AC) = BCWP ACWP
Time
Cost
Planned
Over budget
al Behind Schedule
tu
Ac
n ed
E ar
! Time
Positive CV indicates the project is under-budget.
Negative CV indicates the project is over-budget.
(e) Schedule Variance (SV) = Earned Value (EV) Planned Value (PV) = BCWP BCWS
Cost
Schedule
al
c tu
A
CV
SV
d
rne
Ea
! Time