Activivity Planning in Software Project Management
Activivity Planning in Software Project Management
Chapter Six
Activity planning
• An activity
• Must have clearly defined start and end-points
• Must have resource requirements that can be
forecast: these are assumed to be constant
throughout the project
• Must have a duration that can be forecast
• May be dependent on other activities being
completed first (precedence networks)
Do B
PERT
Do A Do D
Do C
CPM
Do B
Do A
Do D
Do C
SPM (5e) Activity 9
planning
Drawing up a PERT diagram
7days
Acceptance Install new
testing release
20 days 1day
• Finish to start
Test prototype
2 days
Document
1 day Amendments
SPM (5e) Activity 12
planning
Types of links between activities
• Start to finish
Operate
temporary
system
Float = LF - ES - duration
What is it in this case?
Latest Latest
Float
start finish
EF = day 7
ES =
day10
EF =
day10
SPM (5e) Activity 19
planning
Example of an activity network
FLOAT
LF
ES
activity
0 4w
4w 44 7 1w 8 10 2w 12
BB D E
5 5 9 9 2 10 10 0 12
0 10w 10
A
0 0 10
B can be a further 2 days late – affects
D but not the project end date =
interfering float
SPM (5e) Activity 28
planning