Professional Documents
Culture Documents
Planning
Execution
To help guide you
through the process
you need a
roadmap of some
type
Controls
Closeout
DR. ZEESHAN BHATTI
FIGURE 1.1
14
Purpose
Work
Breakdown
Structure
Responsibility
Matrix
R
Project Background
Gantt
Network
Resource
Plan
Budget
A
A
Project Deliverables
S
R
TIME
Perform
Tasks
PROJE
CT
LEADERSHIP
AR
NED
S
RE
EN
LE
PO
RT
Track
Progress
SO
LES
EOS
CL
COMMUNICATION
O
UT
Evaluate
Success
ME
S
I NG
Conduct
Close-Out
Meeting
Share
Lessons
Learned
BOOK
E
T
ET
PLAN
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
Project schedule
Resource plans/histograms
Budget
DR. ZEESHAN BHATTI
PROJECT NOTEBOOK
Project Pre-plan
Background information
Customer data
Third-party data (vendors, suppliers, etc.)
Project Plan
Project Implementation
Meetings (agenda/minutes)
Team/management/customer/third party progress
reports
Customer change requests/decision matrix issue
resolution forms/reports
Project Close-out
Final evaluation of measurable success
indicators
Close-out meeting (agenda/minutes)
Final project report
Reference letters
Lessons learned
Project Administration
Contractual documents
Invoices
Expenses
Correspondence
Contact log
Statement
of Work
Project Background
Project Deliverables
S
R
TIME
PROJE
CT
BOOK
E
T
ME
Perform
Tasks
S
I NG
Project Deliverables
LEADERSHIP
LE
AR
NED
Track
Progress
RE
SO
LES
EOS
CL
COMMUNICATION
O
UT
Evaluate
Success
Budget
ET
Project Background
Share
Lessons
Learned
Resource
Plan
PLAN
Purpose
Conduct
Close-Out
Meeting
Gantt
Network
EN
Purpose
Responsibility
Matrix
PO
RT
Form
Project
Team
Work
Breakdown
Structure
Statement
of Work
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
10
11
12
13
14
S
R
TIME
Perform
Tasks
S
I NG
PROJE
CT
ME
ET
BOOK
E
T
LEADERSHIP
LE
AR
NED
RE
SO
Track
Progress
COMMUNICATION
O
UT
Evaluate
Success
PLAN
LES
EOS
CL
Share
Lessons
Learned
Budget
Project Deliverables
Conduct
Close-Out
Meeting
Resource
Plan
EN
Purpose
Project Background
Gantt
Network
PO
RT
Work
Breakdown
Structure
Form
Project
Team
Responsibility
Matrix
Statement
of Work
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
15
16
Level I
(Noun)
Level II
(Noun)
DELIVERABLE
ACTIVITY
Level III
(Action Verbs)
TASK
(WORK PACKAGE)
PHASE
FUNCTION
"CHUNK" OF
WORK
PROJECT
MANAGEMENT
ACTIVITY
TASK
(WORK PACKAGE)
Level IV
(Action Verbs)
17
Level 1
Level 2
Level 3
Level 4
Level 3
The outline
approach is
used by
Microsoft
Project
Level 2
Level 3
18
Responsibility
Matrix
Project Background
Project Deliverables
ME
Perform
Tasks
LEADERSHIP
COMMUNICATION
SO
LE
AR
NED
Track
Progress
RE
PROJE
CT
TIME
BOOK
E
T
O
UT
Evaluate
Success
S
R
LES
EOS
CL
Share
Lessons
Learned
S
I NG
Conduct
Close-Out
Meeting
A
A
ET
Budget
PLAN
A
A
Resource
Plan
Gantt
Network
EN
Purpose
Responsibility
Matrix
PO
RT
Form
Project
Team
Work
Breakdown
Structure
Statement
of Work
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
19
20
FINALIZE SURVEY
CONDUCT SURVEY
COLLECT SURVEY
DEVELOP SURVEY
SUPPORT
STAFF
SENIOR
MANAGEMENT
MARKETING STUDY
CUSTOMER
RASIC Method
PROJECT
MANAGER
TEAM
MEMBER
LEGEND
R - RESPONSIBLE
A - APPROVE
S - SUPPORT (DOES THE WORK)
I - INFORM
C - CONSULT
R/S
ANALYZE DATA
REPORT RESULTS AND SUGGESTION
I
A
S
21
A = Approve
Approves that the work meets all requirements
S = Support
Does the work
I = Inform
Is kept informed of work status
C = Consult
Is consulted on the work
DR. ZEESHAN BHATTI
22
Purpose
Project Background
Project Deliverables
Work
Breakdown
Structure
Responsibility
Matrix
Network
Resource
Plan
Budget
Gantt
A
A
Gantt
Network
S
R
TIME
Perform
Tasks
PROJE
CT
LEADERSHIP
AR
NED
S
RE
EN
LE
PO
RT
Track
Progress
SO
LES
EOS
CL
COMMUNICATION
O
UT
Evaluate
Success
ME
S
I NG
Conduct
Close-Out
Meeting
Share
Lessons
Learned
BOOK
E
T
ET
PLAN
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
23
24
SCHEDULING
Step 1: Estimate Activity Durations
Step 2: Determine Activity Sequence By Creating a Network
Diagram
Step 3: Calculate the Schedule Using Critical Path Method
(CPM) Procedures
Step 4: Show the Schedule by Drawing Gantt and/or
Milestone Charts
25
i
h
c
f
g
DR. ZEESHAN BHATTI
26
ITERATIVE PROCESS
The plan will evolve as the project evolves
The plan is reviewed and updated as more information
becomes available and uncertainties become less
uncertain
Plan
Plan
Plan
Monitor &
Review
Monitor &
Review
Monitor &
Review
27
Project
Management
Deliverables
Design
Deliverables
Database
Deliverables
GUI
Deliverables
Functional
Deliverables
Produce Use
Cases
Produce Activity
Diagrams
Produce Class
Diagrams
28
USE CASE
Describes a unit of functionality from a users perspective
May be text or diagram
29
Place Order
Retailer
Send Payment
Dispatch Order
Send Invioce
Staff
Priority 2
Raise Purchase Order
Make Payment
DR. ZEESHAN BHATTI
30
31
32
Week
1 2
10 11 12 13 14 15 16
Scheduled Completion
Actual Completion
Under-fulfilled tasks:
Over-fulfilled tasks
C, E, F, I
H, J
33
34
COMPLEXITY
Number of tasks?
Number of people?
Size of Budget?
Number/Nature of constraints
Dependencies between tasks
35
36
TWO METHODS
Activity on Arrow
Traditionally the preferred method
Activity on Node
More popular these days
Supported by most Project Management software tools (i.e. MS Project)
37
ACTIVITY ON ARROW
Arrows are used to represent an activity
Circles are used to represent the points where activities
meet
i.e. the dependency between activities
A
B
C
D
38
ACTIVITY ON NODE
Activities are represented
by boxes
Dependencies are
represented by arrows
joining the boxes
Task A
Task B
Task C
Task D
39
COMPARISON
Task A
Task B
B
C
Task C
Task D
40
DEPENDENCY EXAMPLE
Task
B cannot
startstart
until Task
is complete
Task
B cannot
untilATask
A is complete
Activity
on Node
Activity on Node
Task A
Task B
Activity on Arrow
Task A
Task B
41
Task A
Task K
Task B
Task L
42
Wrong
A
dummy activity
Right
B
43
Precedence Diagram
Method
C
A
44
Logic Connection
Activity
45
EXERCISE 1
Draw the following:
Activity K is dependant on Activity A
Activity L is dependent on Activity B
Activity M is dependent on Activity A and B
46
EXERCISE 2
Draw the following:
Activity K is dependent on activities A and B
Activity L is dependent on activities B and C
Activity is dependent on activity B
47
PROJECT EXERCISE 1
Project 1: Verification of a computer system
The followng table shows the activities required for this project.
Activity
ID
1
2
3
4
5
6
7
8
9
Activity
Test Module A
Test Module B
Test Module C
Test Combined Modules
Check User Documents
Print User Documents
Final Systems Check
Prepare Invoice
Ship to Customer
Immediate Predecessor
none
Test Module A
none
Test Module B, Test Module C
Test Combined Modules
Check User Documents
Test Combined Modules
Final Systems Check
Print User Documents, Final
Systems Check
48
Duration
(Days)
4
6
7
4
5
2
9
1
2
ERRORS IN LOGIC
Looping
Due to a mistake in drawing or to errors in identifying dependent
activities
49
ERRORS IN LOGIC
Dangling
Usually occur when activities are added as an afterthought
Can be avoided by using a single finish node
K
K
LL
Finish
50
PROJECT EXERCISE 2
Project 2: A presentation
The followng table shows the activities required for this project.
Activity
ID
1
2
3
4
5
6
7
8
9
10
Activity
Book Search
Journal Search
Internet Search
Produce Outline
Prepare Handouts
Print Handouts
Produce Visual Aids
Write Speech Notes
Rehearse Speech
Give Presentation
Duration
Immediate Predecessor
(Days)
none
12
Book Search
6
none
15
Journal Search, Internet Search
10
Produce Outline
7
Prepare Handouts
2
Produce Outline
12
Produce Outline
4
Write Speech Notes
10
Print Handouts, Produce Visual Aids,
1
Rehearse Speech
DR. ZEESHAN BHATTI
51
52
B
1
1
2
A
0
2
2 0
F
1
3
3
C
0
3
2
Activity Name
Float
Duration
ES EF LS LF
D
5
1
3 7
G
0
2
7 5
I
0
2
9 7
J
0
1
9
9 10
10
H
3
8
1
6
9
DR. ZEESHAN BHATTI
53
10
Duration
- Critical
- Non-Critical
- Slack/Float
DR. ZEESHAN BHATTI
54
Feb
Mar
April
May
June
Task A
Task B
Task C
Task D
Task E
Task F
- Critical
- Non-Critical
- Slack/Float
DR. ZEESHAN BHATTI
55
56
Purpose
Work
Breakdown
Structure
Responsibility
Matrix
R
Project Background
Resource
Plan
Budget
Resource
Plan
A
A
Project Deliverables
Gantt
Network
S
R
TIME
Perform
Tasks
PROJE
CT
LEADERSHIP
AR
NED
S
RE
EN
LE
PO
RT
Track
Progress
SO
LES
EOS
CL
COMMUNICATION
O
UT
Evaluate
Success
ME
S
I NG
Conduct
Close-Out
Meeting
Share
Lessons
Learned
BOOK
E
T
ET
PLAN
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
57
ASSIGNING RESOURCES
A schedule is not complete until all the resources necessary to complete
the project have been committed or assigned.
58
NON-LABOR RESOURCES
Lab time
Facilities
Prototype parts/systems
Equipment
Materials
Roadmap to Project Management Success
Statement
of Work
Form
Project
Team
Purpose
Work
Breakdown
Structure
Responsibility
Matrix
R
Project Background
Gantt
Network
Resource
Plan
Resource
Plan
A
A
Project Deliverables
S
R
Budget
TIME
Track
Progress
P
OR
T
RE
EN
LE
IM P
SO
E
OS
CL
COMMUNICATION
O EARNED
UT
Evaluate
Success
Perform
Tasks
LEADERSHIP
LES
Share
Lessons
Learned
ME
GS
Conduct
Close-Out
Meeting
OK
EB O
IN
PROJE
CT
OT
ET
PLAN
Update
Plan
Resolve
Issues
Manage
Change
59
Purpose
Work
Breakdown
Structure
Responsibility
Matrix
R
Project Background
Resource
Plan
Gantt
Network
Budget
A
A
Project Deliverables
Budget
TIME
Perform
Tasks
PROJE
CT
LEADERSHIP
AR
NED
S
RE
EN
LE
PO
RT
Track
Progress
TIME
SO
LES
EOS
CL
COMMUNICATION
O
UT
Evaluate
Success
ME
S
I NG
Conduct
Close-Out
Meeting
Share
Lessons
Learned
BOOK
E
T
ET
PLAN
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
60
61
COST BUDGETING
Cost Budgeting involves allocating overall cost
estimates to individual work items in order to
establish a cost baseline for measuring project
performance. Using cost estimates, the WBS, the
project schedule, and cost estimating tools, the
project team develops a time-phased budget.
This budget will be used to measure and monitor
cost performance on the project.
Source: PMI
DR. ZEESHAN BHATTI
62
Top-Down Estimates
Are usually are derived from someone who uses experience and/or information to
determine the project duration and total cost.
Are made by top managers who have little knowledge of the processes used to
complete the project.
Bottom-Up Approach
Can serve as a check on cost elements in the WBS
by rolling up the work packages and associated cost accounts to major deliverables
at the work package level.
Macro Estimates
Micro Estimates
High uncertainty
Fixed-price contract
Unstable scope
Apportion method
Function point methods for software and system
projects
Learning curves
Project Estimate
Times
Costs
WBS FIGURE
Purpose
Work
Breakdown
Structure
Responsibility
Matrix
R
Project Background
Gantt
Network
Resource
Plan
Budget
A
A
Project Deliverables
S
R
TIME
Perform
Tasks
PROJE
CT
LEADERSHIP
AR
NED
S
RE
EN
LE
PO
RT
Track
Progress
SO
LES
EOS
CL
COMMUNICATION
O
UT
Evaluate
Success
ME
S
I NG
Conduct
Close-Out
Meeting
Share
Lessons
Learned
BOOK
E
T
ET
PLAN
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
70
Purpose
Work
Breakdown
Structure
Responsibility
Matrix
R
Project Background
Gantt
Network
Resource
Plan
Budget
A
A
Project Deliverables
S
R
TIME
Perform
Tasks
PROJE
CT
LEADERSHIP
AR
NED
S
RE
EN
LE
PO
RT
Track
Progress
SO
LES
EOS
CL
COMMUNICATION
O
UT
Evaluate
Success
ME
S
I NG
Conduct
Close-Out
Meeting
Share
Lessons
Learned
BOOK
E
T
ET
PLAN
E
L
IM P
Update
Plan
Resolve
Issues
Manage
Change
71
REFERRED NOTES
REFERRED BOOK
72
THANKYOU
Q&A
For Course Slides and Handouts
Blog:
http://zeeshanacademy.blogspot.com/
Facebook:
https://www.facebook.com/drzeeshanacademy
73