Difference between revisions of "IS480 Team wiki 2017T2 Oops Metric"
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
{| style="background-color:#0985A1; color:white padding: 5px 0 0 0; border: 2px solid white" width="100%" height=55px cellspacing="0" cellpadding="0" valign="middle" border="0" | | {| style="background-color:#0985A1; color:white padding: 5px 0 0 0; border: 2px solid white" width="100%" height=55px cellspacing="0" cellpadding="0" valign="middle" border="0" | | ||
− | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white " width="10%" | [[IS480 Team wiki 2017T2 Oops Project Management |<font face = "Serif" color="black"><b> | + | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white " width="10%" | [[IS480 Team wiki 2017T2 Oops Project Management |<font face = "Serif" color="black"><b>Schedule</b></font>]] |
− | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white" width="10%" | [[IS480 Team wiki 2017T2 Oops Metric |<font face = "Serif" color="black"><b> | + | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white" width="10%" | [[IS480 Team wiki 2017T2 Oops Metric |<font face = "Serif" color="black"><b>Risk Management</b></font>]] |
− | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white " width="10%" | [[IS480 Team wiki 2017T2 Oops Risk |<font face = "Serif" color="black"><b> | + | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white " width="10%" | [[IS480 Team wiki 2017T2 Oops Risk |<font face = "Serif" color="black"><b>Change Management</b></font>]] |
− | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white " width="10%" | [[IS480 Team wiki 2017T2 Oops Risk |<font face = "Serif" color="black"><b> | + | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white " width="10%" | [[IS480 Team wiki 2017T2 Oops Risk |<font face = "Serif" color="black"><b>Task Metrics</b></font>]] |
− | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white" width="10%" | [[IS480 Team wiki 2017T2 Oops Risk |<font face = "Serif" color="black"><b> | + | |style="padding:0 .3em; solid #000000; text-align:center; background-color:#f97061; border: 0px solid white" width="10%" | [[IS480 Team wiki 2017T2 Oops Risk |<font face = "Serif" color="black"><b>Bug Metrics</b></font>]] |
− | |||
− | |||
− | |||
|} | |} | ||
<br/> | <br/> | ||
− | |||
<br> | <br> | ||
Revision as of 17:16, 6 November 2016
Home | About Us | Project Overview | Project Management | Project Documentation |
Schedule | Risk Management | Change Management | Task Metrics | Bug Metrics |
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 |