Department of Computing ISYS302: Management of IT Systems and Projects Individual Assignment (20% for ISYS302, 10% for ITEC602) “Work Breakdown Structure & Project Schedules using Microsoft Project” Semester 1, 2018 The Assignment is due by 11:55 pm on Monday, 9th April , 2018 It is expected that he student will draw upon the lecture material from the lectures in Weeks 1 to 4, the practicals and Appendix A in Schwalbe 7E to create the MS Project File. The report counts towards 20% of the final mark of ISYS302 and 10% of ITEC602. There are Two Deliverables: 1) MS Project file in either 2010 or 2013 format 2) PDF file for the Report Please upload your two files by 11:55 pm on 9/4/18. Use your student number for the file names. The MS Project file is submitted through the Assignment 2 iLearn submission tool and the PDF file is submitted through the Turnitin tool. As this is a Turnitin assignment, do not wait until the last minute to submit as Turnitin can take up to 24 hours to process a submission. Your submission time will be time stamped by iLearn. You will fail if 30% or more of the report (excluding references) has been plagiarised. Resubmitting through Turnitin can be very slow, so if you want to pre-screen your submission for plagiarism, you can use the free software Viper: http://www.scanmyessay.com/index.php The usual 10% per day (or part thereof) will apply for late submissions. ISYS302 Assignment One Page 3 Semester 1, 2015 There are two parts to this assignment: 1) Project Schedule (MS Project); 2) Project Report (Word document) Part 1: MS Project (100 marks) Scope Statement: Project Title: Dai-Ichi Corporation Australia (DCA) – SAP Project Phase 1 Date: Prepared by: Project Background: The Dai-Ichi Corporation is a major international player in the mining industry. The head office in Italy has recently completed the rollout of SAP for its European headquarters. The decision has been made to deploy the same platform into the Oceania operations commencing with Australia. Given the distance and time zone difference, a decision was also made to deploy the SAP instance on the cloud. This will facilitate the SAP instance to be managed out of Europe. Final negotiations for cloud resources has been completed between Amazon and Dai-Ichi Europe. The Australian team will be the first Cloud SAP instance for the Dai-Ichi group. As such it was decided to break the project down into different phases. You have been appointed as the project manager of the pilot phase and you have been given the following resources. You team comprises the following: 1) Paulo Mossimo – SAP Expert from Italy – familiar with deploying SAP in house 2) Sanjay Srivastava – Cloud Architect – recently hired from HP with experience deploying Amazon Web Services 3) June Smith – SAP Expert – recently hired from Fujitsu. 4) Larry Jones – Linux Apache, MySQL, C programmer. LAMP Specialist. 5) Jenny Harvey – Linux Admin and LAMP Specialist. Your brief is to set up a test instance of SAP on the AWS cloud infrastructure. You have 12 weeks to get the first instance of the SAP up and running. Since Cloud resources are instant on resources, it is assumed that you can start immediately. A total of 20 Cloud servers are available for you to create the SAP instance. You don’t need to use all of them as they cost $2750.00 per month per instance. The configuration of the Test Instance is as follows: 2 x Database Servers 2 x Application Servers 3 x Web Services Layer Servers ISYS302 Assignment Two Page 4 Semester 1, 2018 Project Resource List Staff No Price Project Manager – yourself 1 $2000 per day Paulo – SAP Expert assume Paulo is available from day 1 1 $2000 per day Sanjay – Cloud Architect 1 $7,500 / Month June – SAP Expert 1 $7,500 / Month Larry Jones – LAMP Stack Specialist 1 $3,500 / Month Jenny Harvey – Linux Administrator + LAMP 1 $3250 / Month Amazon Cloud Infrastructure Instance Price X 86 image – per instance $2,750 per month Software SAP Cloud Instance – Site License for Australia 1 $200,000 JIRA 10 $50 per seat Miscellaneous Costs Qty Price Travel & Accommodation Expenses for Paolo 1 $10,000 per month The management team is very keen on getting this phase completed within the budgeted 12 weeks. You would like to be on time and impress the management team so that you can considered for the next phase of the project. You have decided to adopt JIRA as the issue tracking and project management tool. You used it in your last job/project and feel that it can help you succeed with this large project. Deliverables of Part 1 MS Project File (100 Marks) This component requires some preparation and then data entry into the MS Project file as follows: 1.1 Create a WBS (Work Breakdown Structure for the Dai-Ichi SAP Cloud Pilot. see Schwalbe pg. 198-208) for the above scope of work and translate this into a task list in MS Project 2013. Add dependencies and durations to create a Gantt chart (See Appendix A Schwalbe for detailed instructions on how to use MS Project to create a Gantt Chart). You might want to consider adding regular Steering Committee meetings and communications to specific stakeholders on the progress of the project. Example Tasks to consider (this is not an exhaustive list!) Initiating Define Project Scope, time and costs constraints and high-level requirements (done) Form project team (done) Planning ISYS302 Assignment Two Page 5 Semester 1, 2018 Develop Project Plan, Schedule and Detailed Budget (what you are doing in this assignment) Obtain sign off on plan (signals approval by steering committee to start implementation) Design/Build/Test Detailed requirements gathering Go Live Close out project 1.2 Provide the critical path for your implementation. Illustrate your critical path using a sequence of nodes and edges along the following lines. Figure 6.4: Network diagram illustrating durations & critical path (source: Schwalbe, 2011 p: 221). 1 You may just use the network diagram feature in MS Project to illustrate your point, rather than (re)drawing from scratch. 1.3 Add resources to your Gantt Chart and print a resource based task list (who does what when, view of the project) for your own reference. 1.4 Finalise your pricing and technical specs and calculate your budget. 1.5 Microsoft Project File. 1.5.1. Implement the project scope into MS Project 2013 (or 2010), showing costing and indenting subtasks appropriately. a. Use the outline numbering feature to display the outline numbers. For example your WBS should start with i. 1.0 Initiating… b. Enter any duration or dependencies c. Allocate resources d. Show costing for your staff members e. Document WBS and insert into MS Project. ISYS302 Assignment Two Page 6 Semester 1, 2018 f. Cut and paste into Project Report: i. Gantt Chart ii. Network Diagram showing critical path iii. Resource Schedules Part 2: Project Report (100 marks) 2.1 Create a Word Document that details how the project will be managed. Consult Schwalbe p 161-165 for some hints on how to construct the content of your Summary Project Management Plan. The Project Management Plan (PMP) should not exceed 10 pages excluding diagrams and tables. This is not a full PMP but rather an abridged summary overview plan. As this is not a complicated project, keep the documentation simple and clear. Omit headings that are not applicable. Most of the content you need for the PMP is provided in the scope document above either explicitly or implicitly. Read it carefully to extract, extrapolate and interpret the information required. For example: What are the deliverables of this project? What are the objectives? What are the benefits? – (Hint: There is a big swing towards off-the-shelf software packages to minimize risk. SAP is one example of such an application. Cloud infrastructure also makes such deployments easy, e.g. SAP’s cloud instance can be easily duplicated on Amazon Web Services cloud infrastructure using known configuration templates. This has reduced traditional hardware purchase and deployment lead tiime cycles to almost zero.) How will the project be measured for success? What are the constraints? What are the project controls (Hint Steering Committee)? Do not put version control in your summary PMP. (In a real project, the PMP is a living document subject to change control, and versioning is critical.) You must include the following as a bare minimum: x Objectives x Deliverables x High level technical requirements x Project Management Controls x Resources (See 1.3 above) x Budget x WBS diagram x Schedule (Gantt Chart and Critical Path using the Network Diagram), these should be briefly discussed, including any critical assumptions and dependencies Read it carfully Work only on part 2 after when understood part 1 ISYS302 Assignment Two Page 7 Semester 1, 2018 Marking Criteria for the Report and MS Project File You will be marked according to the following criteria, with a final mark out of 200 (scaled to 20% and 10% of the final mark): Element Excellent to Good (100) Pass (50) Incomplete (25) Report containing WBS, Gantt Charts Strong correlation between report and schedule items. Addresses all required elements of the scope and expected benefits. Completed Resource List. Addresses some of the required elements of the scope and expected benefits Provides an incomplete picture of the success criteria and metrics Addresses few elements of the scope and expected benefits Provides an unclear picture of the success criteria Element Excellent to Good (100) Pass (50) Incomplete (25) MS Project File Demonstrates high level of understanding of Work Breakdown Structure and how to breakdown the structure into essential components into MS Project. Use of MS Project output to support the PMP. E.g. Gantt Chart and Critical Path Analysis Demonstrates some understanding of WBS Ability to articulate how WBS translates to project schedule Ability to use MS Project Demonstrates little understanding of WBS MS Project schedule that has limited correlation to the PMP
