HeaderSIS.jpg

TheBrosCode RiskAssessment

From IS480
Revision as of 23:06, 22 September 2018 by Sean.hoon.2016 (talk | contribs) (Added 1 risk assessment)
Jump to navigation Jump to search
WikiBanner.png

HOME

TEAM

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION

SCHEDULE

TASK METRIC

BUG METRIC

RISK ASSESSMENT

CHANGE MANAGEMENT

PROJECT OVERVIEW -RISK.png
No Risk Type Risk Event Impact Likelihood Category Mitigation
1 Project Management There may be sudden Change Requests that is proposed from the sponsors that may unknowingly increase the scope / functionalities of the mobile app. High High R1 Any Change Request that will require additional scope / functionalities added to the mobile app will require assessment from the team, and is needed to seek advice from supervisor where necessary.
2 Project Management As the target audience of the mobile app can range from unmotivated to obese / overweight individuals, finding such users can be a challenging and sensitive task for the team. High High R1 The team is required to have EARLY planning of User Testing sessions internally and also to liaise with sponsors, to see if it is possible to work together with enterprise or government bodies to assist with the testing of the mobile app.
3 Technical The Frontend / Backend development of the mobile app partially relies on online libraries to help speed up the team's progress, however there might be incompatible versions / outdated libraries. High Low R3 The team is required to research and test the libraries thoroughly before implementing any of it into the mobile app.
4 Project Management There may be last minute changes to the project due to different expectations from the sponsors High Low R3 The team will meet regularly with the sponsors to review the project schedule, project scope and time required for each tasks.
5 Technical Runkicker may not be able to operate on phones that do not meet the minimum SDK version of the app. High Low R3 The team has to ensure that Runkicker supports not only the latest SDK version, but also several older versions in order to reach a wider population.

|- |style="text-align: center; font-size: 10px; background: #ffffff; padding: 8px;"| 5 |style="text-align: center; font-size: 10px; background: #ffffff; padding: 8px;"| Technical |style="text-align: center; font-size: 10px; background: #ffffff; padding: 8px;"| Scope Creep. The Runkicker WMS module may experience changes and addition of unnecessary features. |style="text-align: center; font-size: 10px; background: #ffffff; padding: 8px;"| High |style="text-align: center; font-size: 10px; background: #ffffff; padding: 8px;"| High |style="text-align: center; font-size: 10px; background: #ffffff; padding: 8px;"| R3 |style="text-align: center; font-size: 10px; background: #ffffff; padding: 8px;"| The team must ensure that the specific requirements of this module and its functionalities/features are discussed with the sponsors. Both parties's visions have to be aligned to the fact that the WMS will only showcase features/functionalities that are necessary. |}