The work breakdown structure shown in Figure C-17 is for a final iteration to deploy a new application in a new data center. The ABC company has a contract with Super ISP to host the system, and the ISP will set up the computing environment. ABC will then configure the system software, install the new application, conduct stress tests and tune the system, run beta tests, and then deploy the system into a beta-production status. Using Microsoft Project, create a schedule for this deployment activity. Allow Microsoft Project to automatically schedule the tasks. (Note: One easy way to view the total project length is to make a single highest-level task, with all other tasks demoted beneath it.) Answer these questions:

This is a Gantt Chart view after entering the data. Notice the “red” person icons indicate conflicting resources. 

Here is the same initial project schedule with the time line expanded in the right panel and showing critical path tasks. 

a. Note the resource conflicts. Which resources are over allocated? Which tasks show resource conflicts? Does Microsoft Project schedule the tasks correctly or are there resource conflicts that are unnecessary? Please explain.

b. Show critical path tasks and slack time. Which tasks aren't on the critical path and how much slack time does each have?

c. How many days does the project take? Can you shorten the project by manually scheduling the tasks?

d. Level all the resources. How many days does the project take now? Can you improve it by adjusting resources or rescheduling activities?

Transcribed Image Text:

Te Task Name Duration Start Finish Prede, Resource Names Mar 4, 12 Mar 25. '12 Apr 15, 12 May 6, 12 M Mon 3/5/12 Mon 3/5/12 Fri 3/9/12 Thu 4/26/12 Project Total Set up equipment and system 5 days 39 days 2 Set up servers, etc 12 hrs Mon 3/5/12 Tue 3/6/12 ISP staff O ISP staff 8 hrs Install misc system softwar 4 hrs 3 hrs S hrs Tue 3/6/12 Wed 3/7/12 Wed 3/7/12 4 Configure Os Wed 3/7/12 Technical staff Technical staff Technical staff Technical staff Technical staff NTechnical staff 5. Technical staff 9. Configure Web server Wed 3/7/12 wed 3/7/12 Technical staff 7. Configure DB server Configure email server Configure load monitor Wed 3/7/12 Thu 3/8/12 Thu 3/8/12 6 Technical staff 2 hrs Thu 3/8/12 7 Technical staff Technical staff FFechnical staff 8 hrs Thu 3/8/12 Fri 3/9/12 Technical staff 10 Set up backup system 2 hrs Fri 3/9/12 Fri 3/9/12 5,9 Technical staff 1 Establish Procedures 1.38 days Tue 3/6/12 Wed 3/7/12 Tue 3/6/12 Wed 3/7/12 12 Bug tracking procedures 3 hrs Tue 3/6/12 3 Team leader Team leader Tue 3/6/12 Wed 3/7/12 13 Bug correction procedures 4 hrs 12 Team leader Team leader 14 Release procedures 4 hrs Wed 3/7/12 13 Team leader Team leader 15 Deploy application software 3 days Mon 3/12/12 wed 3/14/12 Mon 3/12/12 Mon 3/12/12 10 Developer Developer 16 Configure production librar 8 hrs Export production system 8 hrs Developer 17 Tue 3/13/12 Tue 3/13/12 16 Developer 18 Create database 8hrs Wed 3/14/12 Wed 3/14/12 17 Developer Developer 19 Conduct stress test 17.13 days Wed 3/7/12 Fri 3/30/12 20 Design volume test cases 24 hrs Wed 3/7/12 Mon 3/12/12 14 Developer[200%) developer(200%) 21 Thu 3/15/12 Wed 3/21/12 17,18,21 Developer[200%] Thu 3/22/12 Fri 3/23/12 Build test files 40 hrs Developer[200N) peveloper(200%) Developer(200%) 22 Load database 16 hrs 21 Developer[200%) Test/modify config/code 40 hrs Deply beta-production 23 Mon 3/26/12 Fri 3/30/12 22 Developer[200%) 24 19 days Mon 4/2/12 Thu 4/26/12 8 hrs Mon 4/2/12 Mon 4/2/12 Tue 4/3/12 25 Stabilize production libs 23 Developer(200%) Developer[200%] Developer[200%) Developer[200 Developert200x) Developer[200xLUser(200) Develeper[200%LUser[200%] Developer(200%) 26 Stabilize production DB 16 hrs Wed 4/4/12 25 27 Thu 4/5/12 Tue 4/3/12 Load production data 16 hrs Fri 4/6/12 26 Developer[200%) 28 Define beta test cases 32 hrs Fri 4/6/12 Developer[200%1,Use Developer[200%],Use Developer[200%] Mon 4/23/12 Thu 4/26/12 27,30 Developer[200%] 25 29 Run beta test 40 hrs Mon 4/9/12 Fri 4/13/12 28 30 Correct production system 40 hrs Mon 4/16/12 Fri 4/20/12 29 Developer(200%) 4/26 31 Clean database 32 hrs 32 Begin Beta-production use O days Thu 4/26/12 Thu 4/26/12 31