1. What is the additional cost for reducing the project time to the required 35

Question

1. What is the additional cost for reducing the project time to the required 35 weeks? Which specific tasks do you recommend crashing in order to achieve this milestone? Breifly explain why you selected those tasks? The aim with question is for you to intuitively select the task(s) to crash in order to bring the project to completion in 35 weeks, and to explain why you chose those tasks to crash. There is no right / wrong answer (per se), this question is asking you to make a judgement call on which task(s) to crash to reach 35 weeks (and why).

2. What is the impact on the crashing solution (from Question #1) if the expected time for task B is increased from seven to nine weeks? (Hint: This is a basic What-If analysis, based on your response to Question #3. Please note that Task B has a large amount of slack.)

3. What is the impact on the crashing solution (from Question #1) if the Expected Time for task D is decreased to seven weeks?

Most Most Most Earliest ExpectedVarlance Duration Normal Crash Latest Task Description Optimistic Likely time Finish Time Start Time Finish Time 10,000 $25,000$5,000 A Requirements2 16.50 C Design 9.33 2 $ 10,000 Revising Documenta Quality assur2 26.5031 tic 1.36 D S 20,000 4 30,000 10,000 10,000 3$15,000$5,000 5,0002 5,000 S H 2950 31 $ 25,000 10,000 40.00

Explanation / Answer

Answer:

1. To reduce the project time to 35 weeks we have to crash activity / activities: The selection of activities that to be carshed has to be carefully selected, keeping in mind that it should produce desired result. To reduce the project time from 40 to 35 weeks, 5 weeks to be crashed in activities that have "zero slack" (zero slack activities falls in critical path, for any reduction in project time duration of critical activities has to reduced). In our scenario, Tasks A, C, D, E, F, J, K. has "zero slack".

2. When the expected time of Task B is increased from 7 weeks to 9 weeks. It would not have any impact of the solution of the previous question. The reason being is that the Task B has a slack of 16.5 weeks. The increase in expected time by 2weeks only reduced the slack time from 16.5 weeks to 14.5 weeks without making any impact on the duration of the project.

3. The expected time for Task D is 7 weeks only (as given in question) and there is no reason for again making it 7 weeks. So, the net impact in the schedule is zero. And hence it dont have any impact of the crashing solution of Question No.01

Thanks.

Related Questions

Navigate

• Browse (All)
• Browse 1
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.