SPM (visualizing progress)
SPM (visualizing progress)
3 Visualizing Progress
Economic Assessment:
After collecting data the project manager willrepresent the collected data
using static picture. We look at some methods of presenting a picture of
the project and its future.
Some of these methods are:
1. Gantt charts
2. Slip charts
3. Ball charts
4. timeline
Gantt charts:
Simplest ,oldest techniques for tracking the project progress
Indicates scheduled activity dates and durations
Reported progress is recorded on the chart (by shading activity bars)
" Note that the Gantt chart is named after Henry Gantt (1861-1919) and so should
not be written in capitals! You could ask students what they think GANTT
stands for before you tell them this to impress this on them. I really find Gantt
written as GANTT very, very annoying and threaten students with instant
failure of the module if they do this!
Justin
Code and test module C loE/P/13
Spencer
Code and test module D loE/P/14
Amanda
Specity overall system
Check specfications
Check module Cspec loE/P/6al
Revlew meetings
" The format of the Gantt chart here differs from the format used in Microsoft
project as the activities for each team member are grouped together. You could
input the details so that they came out in this format, but it would not occur
automatically.
Slip charts:
Provide more striking visual indication of those activities that are not
progressing to schedule
The more the slip line bends ,greater variation from the plan.
A slip chart is a version of the Gantt chart where a line is drawn from top to
bottom. To the left of the line are all the completed activities and to the right
those activities (or parts of activities) that have not been completed.
The more jagged the line, the more it means that that there are some activities
that are lagging to various degrees and some that are ahead of themselves. A
very jagged line means that there is scope for re-planning to move resources
from thOse activities that are ahead to those that are behind.
Purdy
Code and test module B loE/P/12
Justin
Code and test module C loE/P/13
Spencer
Code and test module D lo£/P/14|
Amanda
Specity overall system
Check spedfications
Chedk module C spec loE/P/6a
Revlew meetlngs
Ball charts:
Ball charts
Code and test module A
10/10/05 21/10-06
10/10/05 231008)
Green: On time
Red: Missed the target
The timeline:
> This records the way that targets have changed throughout the project.
> Planned time is plotted on the horizontal axis, and actual time on the vertical
axis. The bendy lines going from top to bottom represent the scheduled
completion date for each activity e.g.
> 'analyse existing system at start this was due finish on the Monday of week 3
and it did finish then
> 'obtain user requirements' was originally planned to finish on the Thursday of
week 5, but at the end of the first week it was rescheduled to finish on the
Tuesday of week 6.
Week number
Planned time
time
Actual 2 3 adstngystem
4 6 8 10 11
Analse
1Week
number
requjrement Plan
ser
Dbtain ofike
layout
thndeIsue
Draft tender