Question

Consider a project with the following information:

Activity	Duration	Predecessors
A	5	--
B	7	A
C	9	B
D	5	B
E	7	C, D
F	6	D
G	4	C
H	7	E, F, G

Activity	Duration	ES	EF	LS	LF	Float
A	5	0	5	0	5
B	7	5	12	5	12
C	9	12	21	12	21
D	5	12	17	16	21
E	7	21	28	21	28
F	6	17	23	22	28
G	4	21	25	24	28
H	7	28	35	28	35

Activity	Duration	Total Float	Resource Hours Needed per Week	Total Resources Required
A	5 Weeks		10
B	7 Weeks		8
C	9 Weeks		7
D	5 Weeks		8
E	7 Weeks		4
F	6 Weeks		6
G	4 Weeks		5
H	7 Weeks		8
			Total

  

1. Calculate the total resources required for this project, and create a Resource Loading table, highlighting the activity float.

2. Consider that the maximum resource hours available per week are 10. Which weeks are overcommitted?

3. What options are available for you to resource-level the project? Re-create the Resource Loading table.

Answer 1

Float = LF - EF

Activity	Duration	ES	EF	LS	LF	Float
A	5	0	5	0	5	0
B	7	5	12	5	12	0
C	9	12	21	12	21	0
D	5	12	17	16	21	4
E	7	21	28	21	28	0
F	6	17	23	22	28	5
G	4	21	25	24	28	3
H	7	28	35	28	35	0

Activity	Duration	Total Float	Resource Hours Needed per Week	Total Resources Required
A	5 Weeks	0	10	50
B	7 Weeks	0	8	56
C	9 Weeks	0	7	63
D	5 Weeks	4	8	40
E	7 Weeks	0	4	28
F	6 Weeks	5	6	36
G	4 Weeks	3	5	20
H	7 Weeks	0	8	56

1.

Resource loading table with resource histogram:

2.

As it is very clear from the resource histogram, weeks starting from week-13 and up to week-23, the resources are overcommitted i.e. more than 10 per week.

3.

The project cannot be completed within 35 weeks' time if the capacity is 10 hours per week. We can use the floats to balance the load but still overshooting happens in-between. This is shown below:

So, the only alternative is to extend the project beyond 35 weeks as shown:

So, the project has to be delayed by 11 more weeks.