assignment
11
174 PROJECT PLANNING TECHNIQUES
11
5.5. Refer to Figures 5.5 a and 5.5 b, and assume the following:
· Assume that tasks 3.2.1.1, 3.2.3.1, and 3.2.4.1 each require 1 person for 2 weeks.
· Assume that task 3.2.2.1 will require 2 persons for 4 weeks.
· Assume that tasks 3.2.1.2 and 3.2.1.3, 3.2.3.2 and 3.2.3.3, and 3.2.4.2 and
3.2.4.3 and will each require 1 person for 1 week.
· Assume that tasks 3.2.2.2 and 3.2.3.3 will require 2 persons for 2 weeks.
· Assume that task 3.2.5 will require 2 persons for 2 weeks.
a. Prepare a schedule network for the 13 tasks, showing sequential and concurrent activities and milestones.
b. P repare a list of the 13 tasks. List the EST, LST, EFT, and LFT for each task.
c. L ist the tasks on the critical path using the ESTs and LSTs.
d. U sing the critical path, list the time needed to complete the 13 tasks.
e. P repare a staffi ng profi le for the 13 tasks using the EST for each task.
5.6. Using the template for work packages in Table 5.3 a, design work packages for 5 of the 12 tasks in Table 5.4 and Figure 5.6 . You will have to “ invent ” some of the missing information; be creative but not ridiculous.
TABLE 5.3A Template for work packages
|
Task identifi er: |
« WBS number and name» |
|
Task description: |
« brief description» |
|
Estimated duration: Resources needed: |
« days or weeks » |
|
Personnel: |
« numbers of people needed to complete this task » |
|
Skills: |
« personnel skills needed to complete this task » |
|
Tools: |
« software and hardware needed» |
|
Travel: |
« to where? for how long?» |
|
Other: |
« other resources needed to complete this task » |
|
Predecessor tasks: |
«t o be completed before this task can begin» |
|
Successor tasks: |
« to start after this task is completed » |
|
Work products: |
« outputs of this task » |
|
Baselines: |
« work products to be placed under version control » |
|
Risk factors: |
« potential problems for this task » |
|
Acceptance criteria: |
«f or the work products of this task » |
TABLE 5.4 A task list
|
Activity number |
Description |
Predecessors |
Duration |
Staff number |
|
2.1 |
Receive approval to proceed |
— |
— |
— |
|
3.1 |
Analyze requirements |
2.1 |
1 |
2 |
|
3.2 |
Design |
|
|
|
|
3.2.1 |
Redesign existing components |
3.1 |
6 |
4 |
|
3.2.2 |
Design new components |
3.1 |
3 |
1 |
|
3.2.3 |
Design interfaces |
3.2.2 |
1 |
2 |
|
3.3 |
Implement code |
|
|
|
|
3.3.1 |
Implement new code |
3.2.2 |
6 |
2 |
|
3.3.2 |
Modify existing code |
3.2.1, 3.2.3 |
5 |
1 |
|
3.4 |
Finish implementation |
|
|
|
|
3.4.1 |
Develop integration plan |
3.2.2 |
2 |
2 |
|
3.4.2 |
Finish unit testing |
3.3.1, 3.3.2 |
2 |
2 |
|
3.4.3 |
Update documentation |
3.3.1, 3.3.2 |
2 |
3 |
|
3.5 |
Integrate and test |
|
|
|
|
3.5.1 |
Develop integration tests |
3.4.1 |
1 |
3 |
|
3.5.2 |
Perform integration tests |
3.4.2, 3.4.3, 3.5.1 |
1 |
2 |
|
3.6 |
Perform acceptance tests |
3.5.2 |
1 |
1 |
|
|
|
|
|
|
m.n = tasks; (x) = activity duration
=
milestones;
1
2
3
4
6
7
8
9
10
5
3.1
3.2.2
3.2.3
3.3.1
3.4.1
3.5.1
3.4.3
3.4.2
3.5.2
3.6
(1)
(3)
(6)
3.3.2
(5)
(2)
(0)
(2)
(1)
(1)
(1)
(1)
(6)
(2)
3.2.1
weeks
16
2.1
n
critical path
FIGURE 5.6 A critical - path activity network
T ABLE 5.5 Milestones for the schedule network in Figure 5.6
|
Event |
Description |
|
1 |
Project initiation |
|
2 |
Requirements analysis completed |
|
3 |
Design of new components completed |
|
4 |
Existing components redesigned; interfaces to new components designed |
|
5 |
Integration plan completed |
|
6 |
New code implemented; existing code modifi ed |
|
7 |
Documentation updated |
|
8 |
Unit testing completed; documentation updated; integration tests ready |
|
9 |
Integration tests completed |
|
10 |
Acceptance tests completed |