project management lecture resource analysis. introduction project planning gantt chart and wbs...

Project Management

LectureResource Analysis

Introduction Project planning

Gantt chart and WBS

Project planning Network analysis I

Project planning Network analysis II


Plan Project planning

Resource analysis Risk management Quality Budgets and cost

control Project teams

Project planning Resource analysis

Risk management Quality Budgets and cost

control Project teams

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

Resources Resources may be: Storable

Remains available if not used and is only depleted by usage

Examples? Non-Storable

Availability has to be renewed for each time period

Examples?

Loading The assignment of work to an

operator, machine or department When too much work is required of a

resource it is overloaded If too little work is assigned to a resource

it is underloaded What are the implications if a

resource is underloaded?

Limits Time limited projects – Projects where

time is the overriding factor They must be completed by a certain date

Resource limited projects – Limited resources are available to complete the project

Think about the relationship between time and resources in a project?

Units of resource It is desirable when possible to state the

work required in units of time. (i.e. person/machine hours)

Example To dig a hole 4m x 4m x 6m = 96m3 will take

one person 12 hours. So 96m3 = 12 person hours of digging Or 1 person hour of digging = 8m3

How long would it take 12 persons to dig the hole?

Units of resource Most tasks will NOT have a linear

relationship between the units of resource employed and the activity duration

IS Team working factors? Communication overhead? Increased likelihood of sickness?

Linear vs. non-linear relationship

Relationship Between Unit Resource and Work

0

2

4

6

8

10

12

14

16

18

20

22

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Persons

Per

son

Ho

urs

Linear Relationship Non-Linear Relationship

Exercise 1 – Resource Analysis

Project 1: Verification of a computer systemThe followng table shows the activities required for this project.

Activity ID Activity Immediate Predecessor

Duration (Days) Resources

1 Test Module A none 4 52 Test Module B Test Module A 6 53 Test Module C none 7 104 Test Combined Modules Test Module B, Test Module C 4 155 Check User Documents Test Combined Modules 5 106 Print User Documents Check User Documents 2 57 Final Systems Check Test Combined Modules 9 58 Prepare Invoice Final Systems Check 1 59 Ship to Customer Print User Documents, Final

Systems Check2 5

Exercise 1

0 4 4

0 0 4

1. Test Module A

4 6 10

4 0 10

2. Test Module B

0 7 7

3 3 10

3. Test Module C

10 4 14

10 0 14

4. Test CombinedModules

14 5 19

16 2 21

5. Check UserDocuments

14 9 23

14 0 23

7. Final SystemCheck

19 2 21

21 2 23

6. Print UserDocuments

23 2 25

23 0 25

9. Ship toCustomer

23 1 24

24 1 25

8. Prepareinvoice

0 0 0

0 0 0

Start

25 0 25

25 0 25

Finish

Draw a Gantt chart using earliest Start/Finish Times

Resource analysis Earliest Start Time

Task 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 281 52 53 104 155 106 57 58 59 5


Task 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 281 52 53 104 155 106 57 58 59 5

Now add the resource usage histogram


Task 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 281 52 53 104 155 106 57 58 59 5

Res2015105

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

Exercise 1

0 4 4

0 0 4

1. Test Module A

4 6 10

4 0 10

2. Test Module B

0 7 7

3 3 10

3. Test Module C

10 4 14

10 0 14

4. Test CombinedModules

14 5 19

16 2 21

5. Check UserDocuments

14 9 23

14 0 23

7. Final SystemCheck

19 2 21

21 2 23

6. Print UserDocuments

23 2 25

23 0 25

9. Ship toCustomer

23 1 24

24 1 25

8. Prepareinvoice

0 0 0

0 0 0

Start

25 0 25

25 0 25

Finish

Draw a Gantt chart using latest Start/Finish Times

Resource analysis Latest Start Time

Task 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 281 52 53 104 155 106 57 58 59 5

Now add the resource usage histogram


Task 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 281 52 53 104 155 106 57 58 59 5

Res2015105

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28


Res2015105

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

Res2015105

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

Earliest Start Time

Different types of resource It is likely that more than on type of

resource is being consumed by a project

For three types of resource we need three histograms

(See example in Lockyer and Gordon)

Resource Analysis The same approach can be used to

calculate the: Cumulative Resource Requirements Average Resource Requirements (using

earliest start and latest start)

See (Lockyer and Gordon, 1996)

Levelling Resources Resources can be levelled by:

Moving activities with float Splitting up activities

Only really effective for those with float Mooving activities with no float

Trade-off between extending project duration and reducing resource costs

Sometimes there is no choice

Levelling Resources After resource levelling the Activity

Network must be reviewed Some tasks will now have no usable float

(due to resource constraints) This can be indicated by using “dummy”

activities such as “Waiting for programmer availability”

It is likely that more than on type of resource is being consumed by a task

Project Effort Estimation Need to know:

Usual efficiency of working Sickness/absenteeism rate Other existing commitments (e.g. other

projects) Additional tasks (e.g. routine maintenance) Holidays Constraints on Facilities (e.g. availability of labs) Cost of and availability of overtime etc.

Software Effort Estimation Needs Historical Data KLOC is not a good measure on its

own Complexity of the software can effect

time taken for development E.g. more efficient algorithms will take

longer to design

Laws of Estimation Parkinson’s Law

“Work expands to fill the time available” Brookes’ Law

“putting more people on a late job makes it later”

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

Introduction Project planning

Gantt chart and WBS

Project planning Network analysis I


Plan Project planning

Resource analysis Budgets and cost

control Quality Risk management Project teams