Project Risk Analysis and Risk Management Plan It is generally agreed that the stage of the system development life cycle known as analysis is the most important phase. Even though the success of a project is dependent on a number of different aspects, it is arguable that the most important aspect of a project's success is correctly capturing the requirements at an early stage. According to the principles of project management, a project is deemed a failure if it is unable to fulfill the needs of the end user. However, in order to provide business analysts a sufficient amount of time to develop logical models, it is necessary to gather requirements in a timely manner. Risk Analysis and Risk Management Plan This section of the report focuses on the potential risks that can pose a challenge to the project and the plan to mitigate the impact of these risks. Potential risks for this project ● Loss of documents including code ● Absence of team members ● Failure to meet deadlines ● Poor communication ● Power related risks Tasks Mentioned below are the key tasks of the project. ● Understanding Stakeholders’ requirements ● Research and developing a requirement plan ● Planning ● Training ● Designing ● Development ● Testing and Deployment ● Maintenance until the handover Dependencies Due to the hybrid nature of the company, the effective completion of the tasks will be contingent on the completion of the activities that came before them. For instance, before it was indicated that the completion of job one is necessary for the successful completion of task two. System Administration, Security, Backup, and Recovery When you make a backup of your data, you produce a copy of that data that you may use to recover the original data in the event that it is lost. These mistakes may be the result of defective hardware or software, corrupted data, or a human error such as a targeted attack or an unintended deletion. Other possible causes include corruption of the data and malfunctioning hardware or software. Nevertheless, consideration of it has been included in the strategy for risk management for the current scenario. Scope Administration and Change Control Procedure It was very necessary to use efficient change control procedures in order to keep the system documentation as accurate as possible. A significant portion of the documentation 3 included highly animated graphics, tables, and textual text. Because of the complexity of the process, the team needed a powerful control management system; they utilized GitHub for this.

1. Feeders: An Online Food
Ordering System
Akhil Patel
California Miramar University
CIS 6190 (MSCIS)- Capsonte
Professor Elizabeth McGuire

2. Overview
● Project Risk Analysis and Risk Management Plan
● Project Costs
● Staffing & Resources, Dependencies, and Schedule
● Integration of Internal and External Systems
● System Administration, Security, Backup, and Recovery
● Scope Administration and Change Control Procedure

3. Project Risk Analysis and Risk Management Plan
The analysis stage of the system development life cycle is considered the most crucial step.
Though a project's success depends on multiple factors, capturing the right requirements
at an early stage is arguably the essential element of a project's success. The project
management principles claim that when a project doesn't meet the user's requirements,
the project is considered a failure . However, collecting the requirements timely provides
an ample amount of time to business analysts to create logical models.

4. Project Risk Analysis and Risk Management Plan
Potential risks for this project
● Loss of documents including code
● Absence of team members
● Failure to meet deadlines
● Poor communication
● Power related risks

5. Project Risk Analysis and Risk Management Plan
Risk management Plan
● The team used a cloud supported platform - Google Docs- for saving all the documents. The
platform allows the team members to access the saved records anytime.
● Though all team members had discrete responsibilities, they learned all the necessary skills
required to make uninterrupted progress during the project.
● The team used a smart project chart where each member could track the progress of every task.
The calendar also had a reminder system, which helped the members in accomplishing the tasks on
time.

6. Project Risk Analysis and Risk Management Plan
Risk management Plan
● Weekly review on progress also helped gauge the effectiveness of efforts and come up with the
counter plan. Moreover, these meetings also helped get all team members' ideas and assisted in
finding out tools like smart calendar and GanntPro.com to measure the progress and communicate
in case of conveying ideas.
● Team members worked on Battery-powered laptops. And while working, they made sure that their
devices were fully charged, and the planned meeting places also had power facilities. All team
members also purchased power banks for laptops to cope with any unwanted situation.

7. Project Costs

8. Tasks
● Understanding Stakeholders’ requirements
● Research and developing a requirement plan
● Planning
● Training
● Designing
● Development
● Testing and Deployment
● Maintenance until the
handover

9. Dependencies
As the nature of the business is hybrid for the successful execution of the tasks will be
depended on the previous tasks. For instance, in previous slide the task two depends on the
execution of the task one.

10. System Administration, Security, Backup, and
Recovery
When you create a backup, you make a duplicate of your data that you can restore if your
main data is lost. These errors may be the consequence of faulty hardware or software,
corrupted data, or a human error like a targeted attack or an unintentional deletion.
However for the given case, it is addressed in the risk management plan.

11. Scope Administration and Change Control
Procedure
Effective change control methods were crucial in maintaining the accuracy of system
documentation. Much of the documentation contained diagrams, tables, and written text that was
extremely dynamic. The process's sophistication required a robust control management system; team
used GitHub.