Referencing Styles : Harvard Students will be allocated to groups with 5 to 6 students per group. Each group is required to submit a detailed written report on The PCNet Project (A): Project Risk Management in an IT integration Project case study. 100% of the Assignment2 overall mark is allocated to the written report on the case study. 21 Case Synopsis: The case describes a large and complex IT integration project, after the acquisition of one metals mining company by another. As part of the integration, 40,000 PCâ€™s, applications, and the network had to be consolidated into one system. The project lasted two years and involved 1,000 people across the organisation. The Case illustrates competent project risk management, including risk identification, assessment, and management. With this case, the methods of project risk management, including their implementation and limitations, can be discussed. Designed to examine the process of project management, this case explores the issue of how the design, development strategy, project organization and project personnel are interrelated. Case Assignment Questions: 1. Evaluate the project definition phase of the The PCNet Project (A): Project Risk Management in an IT integration Project. How do the problems that emerged during the project relate to how the project definition phase was managed? 2. Evaluate the role of the The PCNet Project manager (Jack Muller) in the case. What skills do you think are required to be the project manager for the project? 3. Evaluate how well risk was managed in The PCNet Project (A): Project Risk Management in an IT integration Project. You should use the four stage Risk Management framework from the module in answering this question. 4. Given the situation that Jack Muller finds himself at the end of the case, evaluate all of the options available to him and recommend the course of action your group thinks he should take? How should he calibrate the progress hiccups to Max Schmeling and the Integration Management team? How would they react? Guidelines for the written assignment: ï‚§ The report should contain a minimum of 2500 and a maximum of 3000 words. The word count is from the start of the Executive Summary to the end of the Conclusions sections and does not include the cover page, references and appendices. ï‚§ The required format for the layout of the report is as follows: o Cover page as per UCD specifications. 22 o Executive Summary ï‚§ In a single paragraph, summarise the contents of the entire report. This should written last when the rest of the report is completed, so that you know what you are summarizing. o Introduction to the selected project ï‚§ Briefly give an introduction to the project you have chosen to analyse. ï‚§ Outline your plan to analyse the project, i.e. what topics you will use and the elements of theory or frameworks within those topics you will apply to the project. o Analysis of the Project ï‚§ Using the theory in the module topics, analyse the project. ï‚§ You should not spend too many words describing the theory you use (referencing it is sufficient), but devote most of the effort to applying the theory to the information you have obtained about the project. o Discussion and Conclusions ï‚§ In this section, you discuss your findings and explain why the project can be deemed a success or failure â€“ what worked well and why, what didnâ€™t work and why, and what your group would have done differently if you were the project manager. ï‚§ Identify the key learning points in the project and what your group learned from undertaking the assignment. o References ï‚§ All third party material used in the report must be listed here using a formal referencing system such as the Harvard system. These must be correctly cited where used in the body of the report.