Difference between revisions of "IS480 Team wiki: 2016T2 LOCK Project Metrics"
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
<!--Sub Header End--> | <!--Sub Header End--> | ||
− | [[Image:TeamLockOverallWords.png|center|400px]] | + | [[Image:TeamLockOverallWords.png|center|400px]]<br/> |
<!-- Schedule Matrix--> | <!-- Schedule Matrix--> | ||
<br/> | <br/> | ||
+ | [[Image:TeamLockScheduleWords.png|center|400px]]<br/> | ||
===SM Score = Estimated No. of Days in Iteration / Actual No. of Days spent in Iteration=== | ===SM Score = Estimated No. of Days in Iteration / Actual No. of Days spent in Iteration=== | ||
Line 52: | Line 53: | ||
<br/> | <br/> | ||
+ | [[Image:TeamLockBugWords.png|center|400px]]<br/> | ||
<!-- Bug Metrics --> | <!-- Bug Metrics --> | ||
<br/> | <br/> |
Revision as of 17:58, 1 November 2015
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
SM Score = Estimated No. of Days in Iteration / Actual No. of Days spent in Iteration
Score(%) | Action |
---|---|
SM < 50 | Immediately inform Supervisor Ben Gan about the slip within 24 hours. Then use the same mitigation as the category 50 < SM < 90 and seriously consider dropping tasks. |
50 < SM <= 90 | Re-estimate the tasks for the future iterations. Consume buffer days. Analyze cause of delay and make necessary corrections. |
90 < SM <= 110 | Estimates are fairy accurate, and we are roughly on track. Consider add/deduct number of days behind schedule from buffer days. |
110 < SM <= 150 | Gross over-estimated the effort required. Re-estimate the tasks for future iterations and add number of days to buffer days. |
150 < SM | Immediately inform Supervisor Ben Gan about the slip within 24 hours. Then use the same mitigation as the category 110 < SM <= 150 |
Impact Score
Severity | Description |
---|---|
Low Impact (1 ~ 4 points) | Inconsequential. Simple typo error or minor user interface misalignment. |
High Impact (5 ~ 9 points) | Non-critical functionalities are not working, but still system runs. |
Critical Impact (10 points) | The system or core functionality is down. |
Mitigation Plan
Total Score = # Bugs (Low) x 1 + # Bugs (High) x 5 + # Bugs (Critical) x 10
Bug Score | Action |
---|---|
Score <= 10 | Fix during buffer time. |
10 < Score <= 20 | Fix during planned debugging time in current iteration. |
Score > 20 | Halt current development and fix the bug(s) immediately. Reschedules if necessary. |