Haluk Demirkan Project Scheduling Assignment - MS Project The following questions below are to be answered using Microsoft Project (or any other project management software package). In order to turn in your work from MS Project where required, copy the displays from MS Project into a single MS Word document after copying them using the \"copy picture\" or \"print screen\" and paste functionalities. Please make sure that the figures in your answer sheet readable. 1. Initial Work Breakdown Structure Input. A. Consider the Software Development WBS in below. Create a Microsoft Project model for this WBS. Include a WBS column in your Entry Table that includes automatic numbering of the tasks to reflect the WBS hierarchy (do not enter task durations or precedence relationships). Include the entry table for your answer (5 pts). B. Determine how many actual tasks are in the project (that is, how many activities should have durations assigned to them). How many summary activities are there (5 pts)? Software Dev Definition Design Implementation Functional Objectives Identify Interfaces Establish Project Goal Specify I/O, audit, and controls Establish Objectives Confirm data specs and data flow Identify key requirements Technical Requirements Define program specs Obtain current systems documentation Prepare system flows Define new systems requirements Establish data conversion plan Programming Write Source code Write JCL Write Documentation Obtain Approval Installation Perform Testing Perform Training Cut-over Obtain Approval Operation Specify integration test plan Choose SDM Operate System Project Review Obtain Mgt. Approval Obtain Mgt Approval Audit Approval 1 of 6 2/15/2016 Haluk Demirkan 2. Finding the critical path, measuring slack A Six Sigma team at Superchip, a semiconductor manufacturer, must implement a new means of placing serial numbers on the companies' semiconductor chips that may be more easily read by the user. The project is being implemented due to a rash of recent thefts of the company's most popular processor chip, which is used in personal computers. The team has developed the following project network for the project, along with the estimates of activity duration listed on the network. All durations are in weeks. Assume that this project is scheduled to begin on August 7, 2006. B 3 D 5 I 7 E 1 A 2 H 7 J 1 F 6 C 5 G 6 A. Input the project data to MS Project. What is the project completion date (5 pts)? B. What is the Critical Path and what is its duration (5 pts)? C. Which activities have slack, and how much slack do they have (5 pts)? Provide total and free slacks. D. If activity B's duration were extended to 9 weeks, how would the project duration be affected (5 pts)? 3. Project Input and Listing the Critical Path When an accounting firm audits a corporation, the first phase of the audit involves obtaining \"knowledge of the business.\" An example of this phase of the audit is illustrated by the activities listed in the WBS in Table 3.1, where each activity (task) is listed along with its duration in days, its predecessors, and resource requirements (accountants) for each activity. The accountants work a standard 40 hour work week, 5 days per week, and the project will begin January 5, 2004. A. Determine the minimum duration schedule for this project assuming that tasks start at their early start dates given precedence relationships, and ignoring resource constraints. Include the Microsoft Project Entry Table and Gantt chart with your answer (5 pts). B. What is the critical path for this project (5 pts)? C. Compare the duration shown in the project summary task for the answer to part A solution with the number of calendar days required to complete the project. Explain any difference (5 pts). Table 3.1 Audit Project Activity Predecessors A A C D B,E F Audit Project A. Determine terms of engagement B. Appraise auditability risk and materiality C. Identify types of transactions & errors D. Describe systems E. Verify systems descriptions F. Evaluate internal controls G. Design audit approach 2 of 6 Duration Resources 3 6 14 8 4 9 10 1 1 2 1 2 2 2 2/15/2016 Haluk Demirkan 4. Scheduling Subject to a Resource Constraint Consider again the project in problem 3. Given the all of the data in Table 3.1, the project manager for the auditing project is now faced with a resource constraint. There are only two accountants available to work on this project, at a rate of $75.00 per hour. A. Enter the resource requirements shown in Table 3.1 into your MS Project model, and demonstrate that the schedule found in problem 3 leads to an over-allocation of accountants during the project. Include an MS Project resource graph with your answer showing the over-allocation (5 pts). B. Use the automatic resource-leveling feature in MS Project to determine a schedule that does not lead to an overallocation of accountants, and which is still completed in the same amount of time as the answer to problem 3. Include the Gantt chart and resource graph with your schedule (5 pts). C. Determine the total cost for the accountants under this schedule. Include an MS Project Cost Table with your answer that shows the cost for each activity (5 pts). 3 of 6 2/15/2016 Haluk Demirkan 5. Short Case: Developing and Rolling out the On-Line Bill Pay Service at Meridian BankCorp Sam Power, CEO of Meridian BankCorp has asked his Information Technology V.P., Susan Hill, to make an important addition to their on-line banking services, an electronic bill pay service as soon as possible. Hill, an ASU graduate, has decided to work with an Applied Project team of ASU MBA students to develop the new service as a part their applied project course. During the bidding process for Applied Projects, your team decided that despite the recent downturn in e-business development, you still believe that e-business is important to your future. As a result, you stated that the Meridian BillPay project was your first preference, and your team was assigned to assist Meridian in developing a project plan for assisting in the planning and rollout of the new service. Since the project requires both Marketing and Information Management expertise, your team consists of six members: three from the MSIM track, and three from Services Marketing and Management. All team members are expected to be able to perform all project activities; therefore resource planning activities should be performed under the assumption that this is a team of six equally skilled individuals. The goal for the project is for your team, working together with Meridian personal, to develop, market test, and rollout an online bill pay service at Meridian. The project will begin on January 11, 2006 and must complete for a final presentation by May 15, 2006. 5. Part A: Initial Schedule Hill has delegated the task to a project manager from Meridian, Sally Power and your team, as well as additional personnel from Meridian. Working together, your team has developed an initial project Work Breakdown Structure, along with commensurate task durations and sequence relationships among activities. The WBS, including activities, durations and sequence are listed in Table 5.1 below. Items without durations are higher-level WBS processes. The task durations are based on project team work weeks; that is, a 1 wk duration represents 1.5 work days. Thus, the work week calendar for the team was established as Weds. afternoon and Friday of each week, representing 12 hours per team member per week, based on the team's available hours. They are also available on Saturday's, as needed. As of today, the team has completed the WBS development, and must arrive at a project schedule. 1. Beginning with the start and completion dates listed above, input the data to Microsoft Project, and determine whether the project can be completed by May 15, 2006 (project completion date), given that the project must start no earlier than January 11, 2006 (project start date) (10 pts). 2. List the dates for each milestone, and the completion date for the project, if other than May 15. Include a print-out of the MS Project Gantt Chart and input table with your answer (10 pts). 5. Part B: Resource Planning 1. The resource requirements for your team members for each project activity are listed in Table 5.2. Using Microsoft Project, determine whether you can meet the May 15 due date by using the resource leveling feature. Each team member is available to work on the project 12 hours per week, thus work week will need to be modified within your project model. There are six team members. The resource requirements represent the number of team members required for 12 hours per week. Again, provide the Gantt chart and input table with your answer (10 pts). 2. If the schedule provided in (1) does not meet the project due date, suggest changes in resource calendars and assignments that will allow you to meet the project due date. One team member has suggested that the team schedule an additional two hours on Saturday morning to work on the project. Will this be sufficient, or would you suggest additional changes? Provide a feasible schedule shown in a Gantt chart to justify your answer (10 pts). 4 of 6 2/15/2016 Haluk Demirkan Table 5.1. Work Breakdown Structure, Activities, Durations, Sequence Activity Number Activity Duration 0 Phoenix rollout, Bill Pay 1 Final Project Plan 1 wk 2 Regulatory application & approval 3 Prepare application to state 1 wk 4 File with State Regulators 2 wk 5 Milestone: Obtain regulatory approval 2 hrs 6 Web Page Design 7 Prototype web page design 2 wk 8 Prototype security check 1 wk 9 Milestone: Prototype Approval 2 hrs 10 Local Market Survey 11 Survey Design .5 wk 12 Survey execution 2 wk 13 Analyze survey results 1.5 wk 14 Develop Marketing plan 2 wk 15 Final Page and System Design 16 Final design .5 wk 17 Code pages 2 wk 18 Systems test, final design 1 wk 19 Milestone: Final design approval 2 hrs 20 Web Site Security system 21 Final security analysis .5 wk 22 System security system dev. 2 wk 23 Approve final system 2 hrs 24 Implement production system .5 wk 25 Final integration and site test 26 Web site integration 2 wk 27 Test design .5 wk 28 Execute test 1 wk 29 Milestone: Rollout readiness review 2 hrs 30 Finalize Marketing Plan and Develop advertising campaign 31 Complete marketing plan 2 wk 32 Develop media plan .5 wk 33 Write content 2 wk 34 Design and release advertising to media 1 wk 35 Site Rollout 36 Begin media campaign 1 wk 37 Final preparation for website rollout 2 wk 38 Milestone: Approve Rollout 2 hrs 5 of 6 Predecessor 1 3 4 1 1 7,8 1 11 12 13 9,14 16 17 18 5,8 21 19,22 23 23 26 27 28 14,19 14,19 31,32 33 34 29,24 36,37 2/15/2016 Haluk Demirkan Table 5.2. Resource Requirements Activity Number Activity 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 Phoenix rollout, Bill Pay Final Project Plan Regulatory application & approval Prepare application to state File with State Regulators Obtain regulatory approval Web Page Design Prototype web page design Prototype security check Prototype Approval Local Market Survey Survey Design Survey execution Analyze survey results Develop Marketing plan Final Page and System Design Final design Code pages Systems test, final design Final design approval Web Site Security system Final security analysis System security system dev. Approve final system Implement production system Final integration and site test Web site integration Test design Execute test Rollout readiness review Finalize Marketing Plan and Develop advertising campaign Complete marketing plan Develop media plan Write content Design and release advertising to media Site Rollout Begin Media campaign Rollout website Begin Bill Pay site operations 6 of 6 Team members required 6 4 4 6 3 3 6 4 2 3 2 2 6 3 6 2 2 6 3 3 2 4 6 3 4 2 2 2 2 6 2/15/2016 ID Task Task Name Mode 25 1 2 3 4 5 6 7 8 9 10 11 August 2006 30 04 09 14 19 24 29 September 2006 03 08 13 18 23 28 October 2006 03 08 13 18 23 28 November 2006 02 07 12 17 Superchip A B C D E F G H I J Project: Proj 2 - Six Sigma Date: Wed 19-10-16 Task Manual Task Deadline Split Duration-only Critical Milestone Manual Summary Rollup Critical Split Summary Manual Summary Progress Project Summary Start-only Manual Progress Inactive Task Finish-only Slack Inactive Milestone External Tasks Inactive Summary External Milestone Page 1 22 27 December 2006 02 07 12 17 22 27 Janua 01 January 2007 01 06 11 16 21 26 February 2007 31 05 10 15 Project: Proj 2 - Six Sigma Date: Wed 19-10-16 20 25 March 2007 02 07 12 17 22 27 April 2007 01 06 11 16 21 26 May 2007 01 06 11 16 21 26 June 2007 31 05 10 Task Manual Task Deadline Split Duration-only Critical Milestone Manual Summary Rollup Critical Split Summary Manual Summary Progress Project Summary Start-only Manual Progress Inactive Task Finish-only Slack Inactive Milestone External Tasks Inactive Summary External Milestone Page 2 15 20 25 July 2007 30 05 10 15 20 ID Task Mode 1 2 3 4 5 6 7 8 9 10 11 Task Name Start Finish Late Start Late Finish Free Slack Total Slack S Superchip A B C D E F G H I J Mon 07-08-06 Mon 07-08-06 Mon 21-08-06 Mon 21-08-06 Mon 11-09-06 Mon 11-09-06 Mon 25-09-06 Mon 25-09-06 Mon 06-11-06 Mon 16-10-06 Mon 25-12-06 Fri 29-12-06 Mon 07-08-06 Fri 29-12-06 Fri 18-08-06 Mon 07-08-06 Fri 18-08-06 Fri 08-09-06 Mon 11-09-06 Fri 29-09-06 Fri 22-09-06 Mon 21-08-06 Fri 22-09-06 Fri 13-10-06 Mon 02-10-06 Fri 03-11-06 Fri 15-09-06 Mon 30-10-06 Fri 03-11-06 Fri 03-11-06 Mon 25-09-06 Fri 03-11-06 Fri 03-11-06 Mon 13-11-06 Fri 22-12-06 Fri 22-12-06 Mon 06-11-06 Fri 22-12-06 Fri 01-12-06 Mon 06-11-06 Fri 22-12-06 Fri 29-12-06 Mon 25-12-06 Fri 29-12-06 0 days 0 wks 0 wks 0 wks 0 wks 7 wks 0 wks 7 wks 0 wks 3 wks 0 wks S 07 Aug '06 M T W T 0 days 0 wks 3 wks 0 wks 3 wks 7 wks 0 wks 7 wks 0 wks 3 wks 0 wks Critical Project Summary Manual Summary Rollup Critical Split Rolled Up Critical Manual Summary Task Rolled Up Critical Split Start-only Split Inactive Task Finish-only Milestone Inactive Milestone External Tasks Slack Inactive Summary External Milestone Slippage Manual Task Deadline Summary Duration-only Progress F S S 14 Aug '06 M T W T F S S S 21 Aug '06 M T W T F S S 28 Aug '06 M T W T F S S 04 Sep '06 M T W T F S S 11 Sep '06 M T W T F S S 18 Sep '06 M T W T F S S Critical Project Summary Manual Summary Rollup Critical Split Rolled Up Critical Manual Summary Task Rolled Up Critical Split Start-only Split Inactive Task Finish-only Milestone Inactive Milestone External Tasks Slack Inactive Summary External Milestone Slippage Manual Task Deadline Summary Duration-only Progress 25 Sep '06 M T W T F S S 02 Oc M 02 Oct '06 T W T F S S 09 Oct '06 M T W T F S S 16 Oct '06 M T W T F S S 23 Oct '06 M T W T F S S 30 Oct '06 M T W T F S S 06 Nov '06 M T W 7 wks Critical Project Summary Manual Summary Rollup Critical Split Rolled Up Critical Manual Summary Task Rolled Up Critical Split Start-only Split Inactive Task Finish-only Milestone Inactive Milestone External Tasks Slack Inactive Summary External Milestone Slippage Manual Task Deadline Summary Duration-only Progress T F S S 13 Nov '06 M T W T F S S 20 Nov '06 M T W T F S S 27 Nov '06 M T W T F S S 04 Dec '06 M T W T F S S 11 Dec '06 M T W T F S S 18 Dec '06 M T W T F S S 7 wks 3 wks Critical Project Summary Manual Summary Rollup Critical Split Rolled Up Critical Manual Summary Task Rolled Up Critical Split Start-only Split Inactive Task Finish-only Milestone Inactive Milestone External Tasks Slack Inactive Summary External Milestone Slippage Manual Task Deadline Summary Duration-only Progress 25 Dec '06 M T W T F S S Needing help with number 2. 2. Finding the critical path, measuring slack A Six Sigma team at Superchip, a semiconductor manufacturer, must implement a new means of placing serial numbers on the companies' semiconductor chips that may be more easily read by the user. The project is being implemented due to a rash of recent thefts of the company's most popular processor chip, which is used in personal computers. The team has developed the following project network for the project, along with the estimates of activity duration listed on the network. All durations are in weeks. Assume that this project is scheduled to begin on August 7, 2006. A. Input the project data to MS Project. What is the project completion date (5 pts)? Mpp file attached. Project completion date is 29 Dec 2006 B. What is the Critical Path and what is its duration (5 pts)? Critical path is ACFHJ. Critical path duration is 2+5+6+7+1 = 21 weeks C. Which activities have slack, and how much slack do they have (5 pts)? Provide total and free slacks. Slack & Free slack are as below. D. If activity B's duration were extended to 9 weeks, how would the project duration be affected (5 pts)? Due to increase in Activity B, the project completion time will change and will be 19 Jan 2007. Revised mpp is attached ID Task Task Name Mode 25 1 2 3 4 5 6 7 8 9 10 11 August 2006 30 04 09 14 19 24 29 September 2006 03 08 13 18 23 28 October 2006 03 08 13 18 23 28 November 2006 02 07 12 17 Superchip A B C D E F G H I J Project: Proj 2 - Six Sigma Date: Wed 19-10-16 Task Manual Task Deadline Split Duration-only Critical Milestone Manual Summary Rollup Critical Split Summary Manual Summary Progress Project Summary Start-only Manual Progress Inactive Task Finish-only Slack Inactive Milestone External Tasks Inactive Summary External Milestone Page 1 22 27 December 2006 02 07 12 17 22 27 Janua 01 January 2007 01 06 11 16 21 26 February 2007 31 05 10 15 Project: Proj 2 - Six Sigma Date: Wed 19-10-16 20 25 March 2007 02 07 12 17 22 27 April 2007 01 06 11 16 21 26 May 2007 01 06 11 16 21 26 June 2007 31 05 10 Task Manual Task Deadline Split Duration-only Critical Milestone Manual Summary Rollup Critical Split Summary Manual Summary Progress Project Summary Start-only Manual Progress Inactive Task Finish-only Slack Inactive Milestone External Tasks Inactive Summary External Milestone Page 2 15 20 25 July 2007 30 05 10 15 20 ID Task Mode 1 2 3 4 5 6 7 8 9 10 11 Task Name Start Finish Late Start Late Finish Free Slack Total Slack S Superchip A B C D E F G H I J Mon 07-08-06 Mon 07-08-06 Mon 21-08-06 Mon 21-08-06 Mon 11-09-06 Mon 11-09-06 Mon 25-09-06 Mon 25-09-06 Mon 06-11-06 Mon 16-10-06 Mon 25-12-06 Fri 29-12-06 Mon 07-08-06 Fri 29-12-06 Fri 18-08-06 Mon 07-08-06 Fri 18-08-06 Fri 08-09-06 Mon 11-09-06 Fri 29-09-06 Fri 22-09-06 Mon 21-08-06 Fri 22-09-06 Fri 13-10-06 Mon 02-10-06 Fri 03-11-06 Fri 15-09-06 Mon 30-10-06 Fri 03-11-06 Fri 03-11-06 Mon 25-09-06 Fri 03-11-06 Fri 03-11-06 Mon 13-11-06 Fri 22-12-06 Fri 22-12-06 Mon 06-11-06 Fri 22-12-06 Fri 01-12-06 Mon 06-11-06 Fri 22-12-06 Fri 29-12-06 Mon 25-12-06 Fri 29-12-06 0 days 0 wks 0 wks 0 wks 0 wks 7 wks 0 wks 7 wks 0 wks 3 wks 0 wks S 07 Aug '06 M T W T 0 days 0 wks 3 wks 0 wks 3 wks 7 wks 0 wks 7 wks 0 wks 3 wks 0 wks Critical Project Summary Manual Summary Rollup Critical Split Rolled Up Critical Manual Summary Task Rolled Up Critical Split Start-only Split Inactive Task Finish-only Milestone Inactive Milestone External Tasks Slack Inactive Summary External Milestone Slippage Manual Task Deadline Summary Duration-only Progress F S S 14 Aug '06 M T W T F S S S 21 Aug '06 M T W T F S S 28 Aug '06 M T W T F S S 04 Sep '06 M T W T F S S 11 Sep '06 M T W T F S S 18 Sep '06 M T W T F S S Critical Project Summary Manual Summary Rollup Critical Split Rolled Up Critical Manual Summary Task Rolled Up Critical Split Start-only Split Inactive Task Finish-only Milestone Inactive Milestone External Tasks Slack Inactive Summary External Milestone Slippage Manual Task Deadline Summary Duration-only Progress 25 Sep '06 M T W T F S S 02 Oc M 02 Oct '06 T W T F S S 09 Oct '06 M T W T F S S 16 Oct '06 M T W T F S S 23 Oct '06 M T W T F S S 30 Oct '06 M T W T F S S 06 Nov '06 M T W 7 wks Critical Project Summary Manual Summary Rollup Critical Split Rolled Up Critical Manual Summary Task Rolled Up Critical Split Start-only Split Inactive Task Finish-only Milestone Inactive Milestone External Tasks Slack Inactive Summary External Milestone Slippage Manual Task Deadline Summary Duration-only Progress T F S S 13 Nov '06 M T W T F S S 20 Nov '06 M T W T F S S 27 Nov '06 M T W T F S S 04 Dec '06 M T W T F S S 11 Dec '06 M T W T F S S 18 Dec '06 M T W T F S S 7 wks 3 wks Critical Project Summary Manual Summary Rollup Critical Split Rolled Up Critical Manual Summary Task Rolled Up Critical Split Start-only Split Inactive Task Finish-only Milestone Inactive Milestone External Tasks Slack Inactive Summary External Milestone Slippage Manual Task Deadline Summary Duration-only Progress 25 Dec '06 M T W T F S S Needing help with number 2. 2. Finding the critical path, measuring slack A Six Sigma team at Superchip, a semiconductor manufacturer, must implement a new means of placing serial numbers on the companies' semiconductor chips that may be more easily read by the user. The project is being implemented due to a rash of recent thefts of the company's most popular processor chip, which is used in personal computers. The team has developed the following project network for the project, along with the estimates of activity duration listed on the network. All durations are in weeks. Assume that this project is scheduled to begin on August 7, 2006. A. Input the project data to MS Project. What is the project completion date (5 pts)? Mpp file attached. Project completion date is 29 Dec 2006 B. What is the Critical Path and what is its duration (5 pts)? Critical path is ACFHJ. Critical path duration is 2+5+6+7+1 = 21 weeks C. Which activities have slack, and how much slack do they have (5 pts)? Provide total and free slacks. Slack & Free slack are as below. D. If activity B's duration were extended to 9 weeks, how would the project duration be affected (5 pts)? Due to increase in Activity B, the project completion time will change and will be 19 Jan 2007. Revised mpp is attached