hw1_solutiongg - ESD.36J System and Project Management HW1...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
ESD.36J System and Project Management Master Solution HW1 – UAV Development project Due: 9/18/03 1. Construct a task table from the UAV description. Clearly designate each task with its tag, description and identify immediate predecessors and expected task completion times. See [1, Exhibit I] for an example. Try to arrange the task table in “technological order”. Job no. Description Immediate predecessor Normal time (days) a project start 0 b requirement definition a 10 c engine specification b 3 d vehicle layout b 5 e GFE interface b 8 f fuselage design c, d, e 12 g wing design f 10 h Avionics design e 25 i empennage design g 8 j engine delivery c 30 k vehicle integration h, i, j, l 15 l GFE delivery e 10 m ground testing k 20 n flight testing m 25 o end n 0 2. Create a project graph [1, Exhibit II] by hand or using a computer program. a;0 d;5 e;8 j;30 l;10 i;8 m;20 o;0 h;25 b;10 c;3 f;12 g;10 k;15 n;25 1
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
3. What is the earliest finish (EF) for the project as a whole (in units of work days)? Show how you arrive at this result? EF = 108 work days. The procedure in arriving at an EF is given in the HBR article by Thompson and Wiest on page 4 – 5 of the course reader. The resulting graph is shown below: 10 13 b;10 e;8 l;10 g;10 i;8 n;25 S=0 0 0 10 13 10 15 10 43 18 30 18 28 30 40 40 48 48 63 63 83 83 108 108 F=108 18 18 a;0 d;5 c;3 j;30 f;12 k;15 m;20 o;0 h;25 4. What is the critical path? (e.g. a-b-k-x-z). Highlight the critical path in the project graph from 2. Explain in a few sentences what this means for you as the project manager. Where will you focus your attention? The critical path is a-b-e-f-g-i-k-m-n-o. It is shown in the graph below. Hint in finding critical path: Finding critical path is relatively easy in this simple graph. We should start from the FINISH, and searching “upward” to START. Whenever there is a “sink” (in Kerzner’s terminology), i.e. a situation in which a job has two or more immediate predecessors, the critical path should continue on the path which leads to the predecessor that has a latest EF. Situations other than sink should be straightforward. Critical path determines how quickly a project can finish because the critical path consumes the most time to complete, compared with the other paths in the graph. The other paths are called slack paths. Therefore, in order to increase the possibility that the project can finish on time, the project manager has an incentive to reduce the critical path, unless the slack in the slack path is installed purposefully as a safety valve. Kerzner suggests a few ways of reducing the critical path: Transferring resources from slack paths to critical paths Elimination of some parts of the project Addition of more resources 2
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 7

hw1_solutiongg - ESD.36J System and Project Management HW1...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online