HeaderSIS.jpg

IS480 Team wiki: 2016T1 PolyVision Metrics

From IS480
Revision as of 21:08, 29 August 2016 by Jonathanlee.2014 (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
INSIGHT


Home About Us Project Overview Project Management Project Documentation


Metrics


Task Metric (TM)

TM SCORE = ACTUAL No. of Tasks Completed in Iteration / PLANNED No. of Tasks in Iteration

Score (%) Action
< 50 1. Immediately, inform your supervisor about the slip within 24 hours.

2. Then use the same mitigation as the category 50 < TM < 90 and seriously consider dropping tasks.

50 < TM <= 90 1. Re-estimate the tasks for the future iterations.

2. Deduct the number of days behind schedule from buffer days.
3. If there is no more buffer day, decide the functionalities to drop.

90 < TM <= 110 Our estimates are fairly accurate, and we are roughly on track.

1. Add/Deduct the number of days behind schedule from buffer days.
2. If there is no more buffer day, decide the functionalities to drop.

110 < TM <= 150 Gross over-estimated the effort required.

1. Re-estimate the tasks for the future iterations.
2. Add the number of days gained to buffer days.

150 < TM 1. Immediately, inform your supervisor about the slip within 24 hours.

2. Then use the same mitigation as the category 110 < TM < 150

Bug Metric

FORMULA = 1 x No. of LOW + 5 x No. of HIGH + 10 x No. of CRITICAL

Severity Desrcription
LOW Impact (1 points) Unimportant. Typo error or small User Interface (UI) alignment issues.
HIGH Impact (5 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. We have to fix the bugs to continue.