HeaderSIS.jpg

IS480 Team wiki 2017T2 Oops Metric

From IS480
Revision as of 17:13, 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


Description Motivation Scope X Factor Technologies Used Our Sponsor Poster



Risk Description Consequences Likelihood Impact Mitigation Plan
The sponsor may have 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
Roles and responsibilities not clearly defined Low Low The documentation has to detail all the changes and roles clearly. Handover of the task is important and proper time allocation is necessary
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 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
GPS Function – Parsing the location data into the system Team members don’t know which function belongs to which member High High Team to be trained in the aspects of Geo-location tagging before iteration 4