Project Management: Earned Value Analysis and Change Control, Study notes of Computer Engineering and Programming

Download Project Management: Earned Value Analysis and Change Control and more Study notes Computer Engineering and Programming in PDF only on Docsity!

TOPICS

MONITORING AND

CONTROL

CONTRACT MANAGEMENT

SPM UNIT 4

MONITORING AND

CONTROL

Responsibilities

Assessing progress

Checkpoints – predetermined times when

progress is checked

• (^) Event driven: check takes place when a particular event has been achieved
• (^) Time driven: date of the check is pre-determined Frequency of reporting The higher the management level, generally, the longer the gaps between checkpoints

Red/Amber/Green (RAG)

reporting

• (^) Identify key tasks
• (^) Break down into sub-tasks
• (^) Assess subtasks as:

Green – ‘on target’

Amber – ‘not on target but recoverable’

Red – ‘not on target and recoverable only

with difficulty’

• (^) Status of ‘critical’ tasks is particularly important

Gantt charts

Ball charts

Code and test module A Code and test module B Code and test module C 10/10/ 10/10/ 21/10/ 23/10/ 14/10/ 17/10/ 27/10/ 31/10/ 17/10/ 17/10/05 27/10/ 27/10/ Green: On time Red: Missed the target

The timeline Records the way targets have changd throughout the project

Earned value analysis

• Planned value (PV) or Budgeted cost

of work scheduled (BCWS) – original

estimate of the effort/cost to complete

a task (compare with idea of a ‘price’)

• Earned value (EV) or Budgeted cost of

work performed (BCWP) – total of PVs

for the work completed at this time

Earned value – an

example

• (^) Tasks
  • (^) Specify module 5 days
  • (^) Code module 8 days
  • (^) Test module 6 days
• (^) At the beginning of day 20, PV = 19 days
• (^) If everything but testing completed, EV = 13 days
• (^) Schedule variance = EV-PV i.e. 13-19 = -
• (^) Schedule performance indicator (SPI) = EV/PV i.e 13/19 = 0.

Earned value chart with revised forecasts (AC) (PV) (EV)

Recipients of progress

reports

Progress report IT management Customer management Users Quality assurance Project team

Reporting in PRINCE

• (^) Project Initiation Document (PID)
• (^) End-stage assessment
• (^) Mid-stage assessment
• (^) Highlight report
• (^) Checkpoint report
• (^) Project closure report

Prioritizing monitoring

We might focus more on monitoring certain

types of activity e.g.

• (^) Critical path activities
• (^) Activities with no free float – if delayed

later dependent activities are delayed

• (^) Activities with less than a specified float
• (^) High risk activities
• (^) Activities using critical resources