Risk Management Case Study

XYZ Company is a company that sells vacation packages to several of its beach resorts in Florida, Texas, the Caribbean, and Mexico. The company needs to design, develop, and implement a new enhanced reservation software application system that will provide a competitive advantage among its competitors within the industry. The system should be implemented in order to increase revenues during the peek market. If the system is delayed, they could miss out on revenue opportunities during the peek reservation period starting January 3^rd and ending March 15^th, where sixty-five percent of the reservations for the year are typically booked among potential vacationers. Therefore, the system needs to be fully implemented before January 1^st in order to not lose out on business opportunities. Timing is very important for this project.

System developers that include both programmers and database analyst are currently in short supply. The company currently have the necessary resources but each one is paid on average about fifteen percent below the median salary of these types of resources. Also, one of the programmers has significant health issues. The potential for hurricanes to hit the location of the office is around a twenty-two percent chance during the month of September or October which could cost a delay of approximately five days.

There is a potential to automate some portions with some additional functions that would eliminate some staff in the company but would cost $5000 more and add three more days of development time unless we crash the project by paying overtime to existing resources, costing $9000 more. The company could save another $48,000 per year with these additional functions.

Generally, software projects can suffer with poor code quality and technical risks that the software may not function with current hardware or other existing software. User engagement on a project such as this is very critical, but the company has a history of business users not being interested in software development projects. Additionally, while management is excited about this new software package, many of the business users that will be utilizing the new software typically do not like changes.

In the past, the software development team have had issues with data integrity and security, along with software integration issues during the deployment stage of some of the past projects. Thirty-two percent of the past projects have seen data security issues, twenty percent have seen data integrity issues, and forty-four percent have seen issues with software integration. John Doolittle, who has been the past project manager on other software projects for the company is confident that they should not have any issues, but the business sponsor is not as confident due to these issues affecting past software projects. Additionally, the typical stakeholder engagement is typically low based on past software projects for this company.

Here is the project schedule for the software development project. Click on each milestone to see the associated activities.

Design Task Name Duration Start Finish Resource Names Design 14.5 days Tue 9/14/21 Mon 10/4/21 Review preliminary 2 days Tue 9/14/21 Thu 9/16/21 Analyst software specifications Develop functional 5 days Thu 9/16/21 Thu 9/23/21 Analyst specifications Develop prototype based 4 days Thu 9/23/21 Wed 9/29/21 Analyst on functional specifications Review functional Wed 2 days Fri 10/1/21 Management specifications 9/29/21 Incorporate feedback 1 day Fri 10/1/21 Mon 10/4/21 Management into functional specifications Obtain approval to 4 hrs Mon 10/4/21 Mon 10/4/21 Management, Project proceed Manager Design complete 0 days Mon 10/4/21 Mon 10/4/21 Development Resource Task Name Duration Start Finish Names Development 21.75 days Tue 10/5/21 Wed 11/3/21 Review functional 1 day Tue 10/5/21 Tue 10/5/21 Developer specifications Identify modular/tiered design 1 day Wed 10/6/21 Wed 10/6/21 Developer parameters Assign development staff 1 day Thu 10/7/21 Thu 10/7/21 Developer Develop code 15 days Fri 10/8/21 Thu 10/28/21 Developer Developer testing (primary Wed 15 days Wed 11/3/21 Developer debugging) 10/13/21 Development complete 0 days Wed 11/3/21 Wed 11/3/21Testing Resource Task Name Duration Start Finish Names Testing 48.75 days Tue 10/5/21 Fri 12/10/21 Develop unit test plans using 4 days Tue 10/5/21 Fri 10/8/21 Testers product specifications Develop integration test plans 4 days Tue 10/5/21 Fri 10/8/21 Testers using product specifications Unit Testing 15 days Wed 11/3/21 Wed 11/24/21 Review modular code 5 days Wed 11/3/21 Wed 11/10/21 Testers Test component modules to Wed 2 days Fri 11/12/21 Testers product specifications 11/10/21 Identify anomalies to 3 days Fri 11/12/21 Wed 11/17/21 Testers product specifications Wed Modify code 3 days Mon 11/22/21 Testers 11/17/21 Mon Re-test modified code 2 days Wed 11/24/21 Testers 11/22/21 Wed Unit testing complete 0 days Wed 11/24/21 11/24/21 Wed Integration Testing 12 days Fri 12/10/21 11/24/21 Wed Test module integration 5 days Wed 12/1/21 Testers 11/24/21 Identify anomalies to 2 days Wed 12/1/21 Fri 12/3/21 Testers specifications Modify code 3 days Fri 12/3/21 Wed 12/8/21 Testers Re-test modified code 2 days Wed 12/8/21 Fri 12/10/21 Testers Integration testing complete 0 days Fri 12/10/21 Fri 12/10/21Documentation Resource Task Name Duration Start Finish Names Documentation 30.5 days Tue 10/5/21 Tue 11/16/21 Technical Develop Help specification 1 day Tue 10/5/21 Tue 10/5/21 Communicators Tue Technical Develop Help system 3 wks Tue 11/9/21 10/19/21 Communicators Technical Review Help documentation 3 days Tue 11/9/21 Fri 11/12/21 Communicators Incorporate Help Fri 11/12/21 Tue 11/16/21 Technical 2 days documentation feedback Communicators Develop user manuals Technical 2 days Tue 10/5/21 Wed 10/6/21 specifications Communicators Tue Technical Develop user manuals 3 wks Tue 11/9/21 10/19/21 Communicators Review all user Technical 2 days Tue 11/9/21 Thu 11/11/21 documentation Communicators Incorporate user Technical 2 days Thu 11/11/21 Mon 11/15/21 documentation feedback Communicators Documentation complete 0 days Tue 11/16/21 Tue 11/16/21 Pilot Resource Task Name Duration Start Finish Names Pilot 70.25 days Tue 9/14/21 Tue 12/21/21 Project Identify test group 1 day Tue 9/14/21 Wed 9/15/21 Manager Develop software delivery 1 day Wed 9/15/21 Thu 9/16/21 mechanism Deployment Install/deploy software 1 day Fri 12/10/21 Mon 12/13/21 Team Mon 12/13/21 Mon 12/20/21 Deployment Obtain user feedback 1 wk Team Deployment Evaluate testing information 1 day Mon 12/20/21 Tue 12/21/21 Team Pilot complete 0 days Tue 12/21/21 Tue 12/21/21Deployment Resource Task Name Duration Start Finish Names Tue Deployment 5 days Tue 12/21/21 12/28/21 Determine final deployment Wed Deployment 1 day Tue 12/21/21 strategy 12/22/21 Team Develop deployment Wed Thu Deployment 1 day methodology 12/22/21 12/23/21 Team Secure deployment Deployment 1 day Thu 12/23/21 Fri 12/24/21 resources Team Mon Deployment Train support staff 1 day Fri 12/24/21 12/27/21 Team Mon Tue Deployment Deploy software 1 day 12/27/21 12/28/21 Team Tue Deployment complete 0 days Tue 12/28/21 12/28/21 Post Implementation Review Resource Task Name Duration Start Finish Names Tue Fri Post Implementation Review 3 days 12/28/21 12/31/21 Tue Wed Project Document lessons learned 1 day 12/28/21 12/29/21 Manager Wed Thu Project Distribute to team members 1 day 12/29/21 12/30/21 Manager Create software maintenance Thu Fri Project 1 day team 12/30/21 12/31/21 Manager Post implementation review Fri 0 days Fri 12/31/21 complete 12/31/21 Software development template Fri 0 days Fri 12/31/21 complete 12/31/21Training Resource Task Name Duration Start Finish Names Training 45.75 days Tue 10/5/21 Tue 12/7/21 Develop training 3 days Tue 10/5/21 Thu 10/7/21 Trainers specifications for end users Develop training specifications for helpdesk 3 days Tue 10/5/21 Thu 10/7/21 Trainers support staff Identify training delivery methodology (computer based 2 days Tue 10/5/21 Wed 10/6/21 Trainers training, classroom, etc.) Develop training materials 3 wks Wed 11/3/21 Wed 11/24/21 Trainers Conduct training usability Wed 4 days Tue 11/30/21 Trainers study 11/24/21 Finalize training materials 3 days Tue 11/30/21 Fri 12/3/21 Trainers Develop training delivery 2 days Fri 12/3/21 Tue 12/7/21 Trainers mechanism Training materials complete 0 days Tue 12/7/21 Tue 12/7/21Analysis/Software Requirements Task Name Duration Start Finish Resource Names Analysis/Software Wed 14 days Tue 9/14/21 Requirements 8/25/21 Wed Conduct needs analysis 5 days Wed 9/1/21 Analyst 8/25/21 Draft preliminary software 3 days Wed 9/1/21 Mon 9/6/21 Analyst specifications Develop preliminary 2 days Mon 9/6/21 Wed 9/8/21 Project Manager budget Review software Project specifications/budget with 4 hrs Wed 9/8/21 Wed 9/8/21 Manager, Analyst team Incorporate feedback on 1 day Thu 9/9/21 Thu 9/9/21 Analyst software specifications Develop delivery timeline 1 day Fri 9/10/21 Fri 9/10/21 Project Manager Obtain approvals to Mon Management, Project proceed (concept, timeline, 4 hrs Mon 9/13/21 9/13/21 Manager budget) Secure required Mon 1 day Tue 9/14/21 Project Manager resources 9/13/21 Analysis complete 0 days Tue 9/14/21 Tue 9/14/21Analysis/Software Requirements Task Name Duration Start Finish Resource Names Analysis/Software Wed 14 days Tue 9/14/21 Requirements 8/25/21 Wed Conduct needs analysis 5 days Wed 9/1/21 Analyst 8/25/21 Draft preliminary software 3 days Wed 9/1/21 Mon 9/6/21 Analyst specifications Develop preliminary 2 days Mon 9/6/21 Wed 9/8/21 Project Manager budget Review software Project specifications/budget with 4 hrs Wed 9/8/21 Wed 9/8/21 Manager, Analyst team Incorporate feedback on 1 day Thu 9/9/21 Thu 9/9/21 Analyst software specifications Develop delivery timeline 1 day Fri 9/10/21 Fri 9/10/21 Project Manager Obtain approvals to Mon Management, Project proceed (concept, timeline, 4 hrs Mon 9/13/21 9/13/21 Manager budget) Secure required Mon 1 day Tue 9/14/21 Project Manager resources 9/13/21 Analysis complete 0 days Tue 9/14/21 Tue 9/14/21Week 5 Team Case Study Assignment Risk Management Case Study Case Study Details Grading Rubric Category Points Introduction - Provide a brief introduction to this team paper. 5 Identify 10 potential risks - Based on this case study information and further research 20 of potential risks for software projects, your team identifies at least 10 potential risks. Positive Risks Identified - At least two of the risks identified are positive 10 (opportunities) Analysis of Each Risk - Each risks identified adequately describes the odds a certain risk will occur (probability). Also, each risk identified adequately describes what could 25 would happen if each risk occurred (impact). Risk Responses - Each risk identified has an adequate response that is appropriate to both the project and identified risk. Each risk response should describe how the project 25 will be affected. Conclusion - A summary of the team paper should be presented along with any 5 recommendations that the team has for the organization. References - You should have at least three scholarly resources listed on the last page 10 in APA format along with the appropriate intext citations within the body of the report. Total 100