EPGPM PM Lecture2- Planning v1.3

8/18/2019 EPGPM PM Lecture2- Planning v1.3

1/18

Project Management

Lecture 2: Fundamentals

of Planning

Rishi Mohan Sanwal

IIM Kashipur

Feb 2016


2/18

Revision of last class

Feb 2016 2Project Management Excellence


3/18

Scope management

Feb 2016 Project Management Excellence 3

Scope defines the boundaries of the work being

undertaken. A well defined objective leads to a well

defined scope

–

Business Units / Products – Geography

– Departments, Business Functions (Procurement, Sales,

operations, etc.) and sub-functions

–Time duration

– Functional Scope


4/18

Work Definition - WBS



5/18

WBS Example



6/18

So what can a WBS be used for?


Project

Management

Stakeholders

Management

Activities and

Schedule

Management

Resource

Management

Financials

Management

Risk and

IssueManagement

Objectives

and Scope

Management


7/18

Exercise: Making a WBS

You have been made the in-charge of the project to

convert the Haldwani-Nainital into a 4 lane road. You

need to draw a WBS for the project.

Work together in teams of 2


Time: 10+5 mins


8/18

High level project planning – Gannt Charts


WBS Element Duration Predecessor

H 10 weeks

I 8 weeks H

J 6 weeks H

K 4 weeks J

L 2 weeks JM 4 weeks J

N 4 weeks I


9/18

High level project planning – Gannt Charts



10/18

Timelines

Jul Aug Sep Oct Nov Dec

M i l e s t o n e s

Customer Requirements

Signoff

Final Design Sign-off

Foundation

Construction complete

Centre Launch

High level project planning – Milestone

Charts


Planned Milestone

Actual completion


11/18

Stage Gates – Templates for High level

Planning


Illustrative Data Migration Gate Methodology

Illustrative Stage Gates

used by a company

erecting Bio-fuels plants


12/18

So why do projects get delayed?


....and what can we do about it?


13/18

Analysis of project delays at an illustrative

organization


5.1

1.4

2.5 3.6

17.6

11.4

11.2

6.5

5.1

3.0

1.90.8

0.0

2.0

4.0

6.0

8.0

10.0

12.0

14.0

16.0

18.0

20.0

MS1 MS2 MS3 MS4

A v e r a g e d e l a y ( M o n t h s

Average delay Maximum delay Median

90% of the projects are delayed

(from 51* sample projects)

during execution

The data range selected is for 8departments

~75% of projects (39) started

according to proposal startup

date

Average/Median time delay on

milestones keeps on increasing(from MS1 to MS4)

Key Observations

* Selected by HODs


14/18

Analysis of project delays at an illustrative

organization

Reasons for delay analyzed as per PM inputs


42%

18%

13%

14%

13%Client Approvals

Resource Unavailability

Other (data, clearance etc.)

Change in scope of work

Unrealistic deadlines

Client ApprovalsDeliverables not up to clients

expectations

Change of clients project manager

Change in original clients expectations

Another analysisshowed that 47% of

the projects were

under-staffed !


15/18

So why do projects get delayed?



16/18

5 golden rules for project planning

Rule 1: Right forecasts need right environment

Rule 2: To work on future, learn from past

Rule 3: Build buffers; not padding.

Rule 4: Plan your project on all 6 aspects

Rule 5: A plan also has to be the PM’s baby!



17/18

The Next class

Detailed Scheduling with Networks & Critical Paths

We will have a quiz

Please come prepared with MS Projects installed on

your laptops



18/18

Thank You

Rishi Mohan Sanwal

IIM Kashipur

Feb 2016

Documents

EPGPM PM Lecture2- Planning v1.3