HeaderSIS.jpg

IS480 Team wiki 2017T2 Oops Risk Management

From IS480
Revision as of 22:01, 6 November 2016 by Qrxzhang.2014 (talk | contribs)
Jump to navigation Jump to search
Oopslogo.png
HomeButton.png Home ShakeHands.png About Us Glyphicons 042 pie chart.png Project Overview Calendaricon.png Project Management Tableicon.png Project Documentation


Schedule Change Management Risk Managment Task Metric Bug Metric



Risk Description Consequences Likelihood Impact Category Mitigation Plan
The sponsor has a different change of plans This results in a scope creep and as a result the team mission and schedule might have to different thus jeopardising the delivery of other applications Medium High The client will understand the feasibility based on the change management logs. If the change is highly critical, negotiate for the changes and revise the schedule accordingly. The change will be rejected if the team is unable to handle the workload
Team members are not available for sessions due to unexpected reasons Tasks may be delayed and the schedule may be compromised Medium Medium Remaining team members discuss and come up with a back up plan, and they proceed on the tasks
Timeline estimates are unrealistic The tasks that are completed in one iteration will thus spill over, resulting in unnecessary delay and compromising the time schedule High High The team will discuss and make changes to the timeline and progress together
Team is not familiar with features of Android/R programming Project delays due to incorrect estimates and lower quality as there will be more bugs High High Team to be trained before iteration 2 for Android programming and before iteration 4 R programming
We may wrongly estimate the time take to complete a task The schedule may be influenced and corresponding changes need to be made High High Team needs to meet regularly and make corresponding amendments according to experience
Computer may go down during the development processes The current schedule will be compromised and tasks may be delayed Medium High Team members actively save and back up their codes in dropbox and other code sharing software
Users are not willing to provide real information due to privacy issue Number of registration may be reduced High Medium Team members discuss with users and come up with data that are useful and can be publicly used