Transcript: Hugh:We need to name the project Kent: Let's call it Getta Bill Nonia: Great name Hugh: The project is about replacing our current billing system. Ima: Yes. Replacing it with an cloud-based, accurate, easy to use system. Kent: We need more detail than that Ima: Well, it is going to reduce billing errors by 15%. Hugh: What are some of the requirements we need to be sure it fills? Nonia: The system has to have some audit capabilities. We have to be able generate specific, dynamic reports regarding number of customers billed, total billing for various periods and the ability to drill- down for details. Kent: Let's talk about what the project has to deliver. Ima: It has to deliver accurate data for all of our customers. It has to be an accessible system for all of our billing representatives. It is a cloud based system. Nonia: Remember we cannot do anything to the Financial System of Record except to interface. It's definitely out of scope. Hugh: So what will make this acceptable to our internal and external customers? Ima: Ease of use, transaction speed improved by 30%, dynamic reporting. Billing cycles reduced by 30%. Kent: What milestones are we looking at? Nonia: Customer data must be migrated to the cloud completely by August 25. Development will be complete by August 15. The first Pilot will be complete by September 1. We'll be all done by September 10. Hugh: We're going to need at least one data architect, two developers and some billing representatives for testing, a project manager. We are going to have to decide if we use internal resources or external. If we are going to buy the system or build it ourselves. Nonia:We will also need some test machines before we release this and a test environment. Kent: What does the budget look like? Ima: Labor: Developers: $50,000 Data Specialist $50,000 Software Purchase: $100,000 Project Manager: $50,000 Kent: What is going to hold us back? Nonia: That budget! The schedule!!! Ima: We also have to assume that we won't have to do any troubleshooting with our network. We also to assume that the current customer data is accurate. Kent: Wow! We have a lot to do. That's our scope! Let's start planning the rest of our project!!! ID WAS 11.43 Transfer Data 2 1.42 Map frics 3141 validate Data 4111ther Requiremen from users 5 Tack Name 6 7 3 4 ROS Category Organizational Refer to Section E. Technical Technical 2 1.51 evelop Training with peornal Verador External 1.23 Execute Purchase External IDENTIFY RISK Risk Identified (Description) Network Capadty Failure during upina) Data arrars Customer data integrity Scope definition Users interviewed for gathering of requirements did not the experience nar background to provide information. Root Cause of the Risk Market: Off the shell training modules could be available Low bandwidth *Script errors Database mismatch Field mapping wes Nigative impact wors on Schedule Manning: Significant savings an software purchase if bougth on Black Holiday coming up Friday Risk Impact +/- Negative impact an Schedule Training modules available in the market Negative impact an Schedule users interviewed did Users interviewed did not have experience in Sch the billing departmentality Negative impact an Budget, Positive impacts on Budget Positive impact on Schedule 4 Prob. 3 S 4 PERFORM QUALITATIVE RISK ASSESSMENT Impact impact Impact 05 on on Cost Sch. Quality NEGATIVE RISK S 1 2 1 2 3 1 3 3 4 4 1 5 POSITIVE RISKS 1 1 1 4 Risk Score 3 3.2 24 Risk Owner Network Services Data Architect Data Specialis Project Manager Project Manager Project Manager Risk Strategy +/- -Mitigate Accept -Mitigate -Mitigate + Exploit +Enhance PLAN RISK RESPONSE Risk Response Plan Raview bandwidth requirements Research best vendors for needs Select vender for high bardwich *Conduct network assessment and troubleshoot prior to migration validate date an data sample Be selective when interviewing users. Uhers mint have worked in the billing dpt. two years or mor and must be familiar with billing processes User must have operational & technical background. Enter new actrivitas in WBS to ensure actions are taken Meet with mgm and vendor Delay purchase to Black Friday Gather software requirements Understand features and functionality. Reseach the market for off the shelf modules Mest with vender and team to determins suitability IMPLEMENT RISK PLAN Risk Action Owner Don Testit Developer Nonia Business IData #in/it} MONITOR RISK Ridk Status Hugh Butt (ata architech) Action Active Refer to Section F Active Imma Payne Pro Manager) Expired Imma Payne IProj, Manager Active Imma Payne Proj, Manager Active HOW TO USE THIS DOCUMENT This document is a tool to create the risk register for your project. Please watch the "Getta Byte - Risk Management" video listed on the week 6 Canvas Lesson. Also, review the video transcript. The information in the video for risks IDs 1, 2, and 3 have been entered in the riks register as examples. The student job is to identify 4 negative and 2 positive risks. Two Positive risks have also been identified and entered for you as examples. 1) ID: Enter IDs for the 4 negative and 2 positive you must identified. To Identify individual project risks, review the project tasks located in the Project Schedule-sections E.1 and/or the Gantt Chart - section E.2 2) WBS: Enter the WBS number of the risk you have identified. ther Using the RBS located in this to the right determine the risk category. 3) Task Name: Enter the name of the tasks you have identified as having a risk. 4) RBS Category: Select the risk category by clicking on the any cell on this column to visualize the dropdown menu and make a selection Risk Identified: Enter the risk you have identified and describe it. 6) Root Cause: Determine the root cause of the risk. This information is critical to be able to create a risk plan 7) Impact (+ or -): Select the Impact of the risk on the project objectives by clicking on the any cell on this column to visualize the dropdown menu and make a selection. Project objectives are to keep on target the budget, the schedule, and the quality of the project. If the impact is negative, this is a negative risk. If the impact is positive, This is a positive risk. 5) 8) Probability: Ask the question "what is likelihood of occurrence of the identified risk?" Enter a number between 1 and 5. When the probability of occurrenc is: very high enter a 5, high enter a 4, medium enter a 3, low enter a 2, very low enter a 1 9) Impact: Enter a number between 1 and 5 for columns J, K, and L. When theimpact on the project "XXX" objective is: very high enter a 5, high enter a 4, medium enter a 3, low enter a 2, very low enter a 1 Risk Score: The Risk Score is calculated by multiplying the PROBABILITY of occurrence times the highest risk IMPACT (among C, SC,Q) & dividing the product by 5 for normalization purposes. 10) Risk Owner: The risk owner is a subject matter expert from the core team or from a different department who is familiar with the project task. Therefore the risk owner is suitable to create a risk response plan. Cell in this column has a dropdown menu with particular expertise that could be found within the core team or in other departments. Please select one according to the area of the risk you have identified. 11) Risk Stragegy (+ or -): This column presents Risk respoose strategies for negative & positive risks. Select a suitable strategy. Strategies for negative Risks include: Escalate, Avoid, Transfer, Mitigate, & Accept. Strategies for positive Risks include: Escalate, Enhance, Exploit, Share, & Accept 12) Risk Response Plan: Enter the action plan for the strategy you have selected. 13) Action Owner: The risk owner are in charge to ensure the implementation of the risk response plan, It is a member of the team working of the task 14) Status: Select from the dropdown menu the status of the risk 15) Print Page 1 in PDF, take an snip of it and paste in the Word Document for you course project