HeaderSIS.jpg

IS480 Team wiki: 2017T2 ICON RiskAssessment

From IS480
Revision as of 21:33, 8 February 2018 by Bernita.toh.2015 (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
ICON Banner.jpg


Icon Home.png
Icon TheTeam.png
Icon ProjectOverview.png
Icon ProjectSchedule.png
Icon Documentation.png


PROJECT SCHEDULE TASK METRICS BUG METRICS RISK ASSESSMENT CHANGE MANAGEMENT
ICON riskAssessment.PNG


Risk Type Description Likelihood Consequence Level Mitigation Strategy Action Taken Effectiveness
Business Users may be resistant to the new system and require time to adapt Medium Medium 2 Do thorough system documentation, develop relevant test cases and user tests to gather constant feedback. Developers to provide training sessions and prepare user manual. Relevant test cases and testing procedures have been developed. More actions to follow up in the coming iterations. To be updated
Business Business requirements from the sponsor may change over the iterations High High 3 Ensure that both the team and the sponsor adhere to the agreed scope after each meeting. Adhered to the strategy and constantly reminded the sponsor on the agreed scope. While the team has tried to adhere to the mitigation strategy, the team had to accommodate to changing business requirements to ensure that the system brings values to the sponsor.
Technical User interface development progress may be delayed due to the lack of knowledge in using NodeJS, and Ajax High Medium 3 Spend time to pick up relevant knowledge. PM to include sufficient time in planning the project timeline and iterations for the developers. Spent time to pick up the relevant knowledge. Somewhat effective. While the team was able to develop the user interface rather smoothly, there are still some problems faced.
Technical Data management functionalities development progress may be delayed due to the lack of knowledge in using NoSQL, jQuery and Python High Medium 3 Spend time to pick up relevant knowledge. PM to include sufficient time in planning the project timeline and iterations for the developers. Spent time to pick up the relevant knowledge. Somewhat effective. While the team was able to develop the functionalities smoothly, there are still some problems faced.