HeaderSIS.jpg

IS480 Team wiki: 2017T1 Team Kinetic Metrics

From IS480
Jump to navigation Jump to search

HOME

 

ABOUT US

 

PROJECT OVERVIEW

 

PROJECT MANAGEMENT

 

DOCUMENTATION

 


Kinetic LatestBugMetrics.png
Impact Score
Severity Description
Low Impact (1 ~ 4 points) Unimportant. Typo error or small user interface alignment issues.
High Impact (5 ~ 9 points) The system runs. However, some non-critical functionalities are not working.
Critical Impact (10 points) The system is down or is un-usable after a short period of time. Team needs to fix the bugs to continue development.
Mitigation Plan Total Score = # Bugs (Low) x Individual Bug Score + # Bugs (High) x Individual Bug Score + # Bugs (Critical) x 10
Bug Score Action
Score <= 10 Fix during planned debugging period in the current iteration.
10 < Score <= 20 Fix during planned debugging period in the current iteration.
Score > 20 Team must stop current development and fix the bug(s) immediately. Reschedule tasks to the next iteration if necessary.


Kinetic LatestTaskMetrics.png
TM Score = Number of tasks actually completed / Planned number of tasks to complete
Score (%) Action
TM < 50 Inform project supervisor Patrick Thng about the slip within 24 hours. Then use the same mitigation as the category 50 < FM < 90 and seriously consider dropping tasks.
50 < TM <= 90 Analyse cause of delay and re-estimate the tasks for the future iterations.
90 < TM <= 110 Estimates are fairy accurate, and team is on schedule. Consider adding/deducting number of days behind schedule from buffer days.
110 < TM <= 150 Indicative of an over-estimation of the effort required. Re-estimate the tasks for future iteration.
150 < TM Inform project supervisor Patrick Thng about the slip within 24 hours. Apply the same mitigation steps as the category 110 < FM <= 150


For complete bug metrics: Click here
For complete task metrics: Click here
For complete test cases: Click here