1. Lecture Network Analysis
Project Management
Lecture Network Analysis

2. Plan Introduction Project planning Introduction Project planning
Gantt chart and WBS
Network analysis I
Introduction
Project planning
Gantt chart and WBS
Network analysis I
Network analysis II
Project planning
Resource analysis
Risk management
Quality
Budgets and cost control
Project teams

3. 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

4. PBS Example

5. Use Case Describes a unit of functionality from a users perspective
May be text or diagram
Therefore they provide a good tool for Project Task Planning
They also can determine the nature of the project process
How many development iterations?

6. Use Case Example – Big John’s

7. Use Case Example – Big John’s
Each Use Case Shown can be shown as activities in the PBS
The prioritisation can be used to describe the activities for two development iterations
This will be significantly different to the process if only one iteration was used

8. Gantt Chart Example

9. Gantt Chart Example

10. Gantt chart disadvantages
Not ideal for showing inter-relationships
Locating an activity requires three simultaneous decisions:
Method
Time
Resources

11. Complexity Number of tasks? Number of people? Size of Budget?
Number/Nature of constraints
Dependencies between tasks

12. Why Network Diagrams? Splits up the decision making process into
Method/logic - the order in which tasks have to be completed
Time – estimates for the time to completion can be added to each task
Resources – these can be added and then analysis carried out

13. Two Methods Activity on Arrow Activity on Node
Traditionally the preferred method
Activity on Node
More popular these days
Supported by most Project Management software tools (i.e. MS Project)

14. 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

15. Activity on Node Activities are represented by boxes
Dependencies are represented by arrows joining the boxes

16. Comparison

17. Dependency Example Task B cannot start until Task A is complete
Activity on Node
Task B cannot start until Task A is complete
Activity on Node
Activity on Arrow

18. More complex example Four activities/tasks: A, B, K, L
Activity K is dependent on activity A
Activity L is dependent on activities A and B

19. The problem with AoA The same example in AoA The same example in AoA
Wrong…
Activity K is dependent on activity A
Activity L is dependent on activities A and B
Right

20. 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

21. 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

22. Drawing the network Direction Identifying Tasks
The flow of work is from left to right
Identifying Tasks
Each task is given a unique ID number
ID number is often given in WBS

23. Scale Diagram is not drawn to scale Length and size do not matter
They have no meaning

24. Activity Number Activity Description
What’s in the box?
Earliest Start
Estimated Duration
Earliest Finish
Activity Number Activity Description
Latest Start
Float
Latest Finish

25. Project Exercise 1

26. Errors in Logic Looping
Due to a mistake in drawing or to errors in identifying dependent activities

27. Errors in Logic Dangling
Usually occur when activities are added as an afterthought
Can be avoided by using a single finish node

28. Project Exercise 2

29. Final thought for the day: Erm…
Plan
Project planning
Network analysis I
Network analysis II
Introduction
Project planning
Gantt chart and WBS
Network analysis I
Network analysis II
Project planning
Resource analysis
Risk management
Quality
Budgets and cost control
Project teams
Final thought for the day: Erm…