HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T2 LOCK Project Metrics"

From IS480
Jump to navigation Jump to search
Line 34: Line 34:
 
|-
 
|-
 
| SM < 50
 
| 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.
+
| Very Late
 
|-
 
|-
 
| 50 < SM <= 90
 
| 50 < SM <= 90
| Re-estimate the tasks for the future iterations. Consume buffer days. Analyze cause of delay and make necessary corrections.
+
| Slightly Late
 
|-
 
|-
 
| 90 < SM <= 110
 
| 90 < SM <= 110
| Estimates are fairy accurate, and we are roughly on track. Consider add/deduct number of days behind schedule from buffer days.
+
| On Time
 
|-
 
|-
 
| 110 < SM <= 150
 
| 110 < SM <= 150
| Gross over-estimated the effort required. Re-estimate the tasks for future iterations and add number of days to buffer days.
+
| Slightly Early
 
|-
 
|-
 
| 150 < SM
 
| 150 < SM
| Immediately inform Supervisor Ben Gan about the slip within 24 hours. Then use the same mitigation as the category 110 < SM <= 150
+
| Too Early
 
|}
 
|}
  

Revision as of 18:16, 1 November 2015

LockLogo3.jpg


LockHouse.png   HOME LOCK-About Us.png   ABOUT US LockGraph.png   PROJECT OVERVIEW LockManage.png   PROJECT MANAGEMENT LockDocuments.png  DOCUMENTATION

 


TeamLockOverallWords.png


TeamLockScheduleWords.png

Schedule Tracking Category

Score(%) Mitigation Action
SM < 50 Very Late
50 < SM <= 90 Slightly Late
90 < SM <= 110 On Time
110 < SM <= 150 Slightly Early
150 < SM Too Early

SM Score = Estimated No. of Days in Iteration / Actual No. of Days spent in Iteration

Score(%) Mitigation 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


TeamLockBugWords.png

Impact Score

Severity Description
Low Impact (1 - 4 points) Inconsequential. Simple typo error or minor user interface misalignment.
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 unstable after a short period of time. Bug fix immediately to continue

Mitigation Plan
Total Score = # Bugs (Low) x 1 + # Bugs (High) x 5 + # Bugs (Critical) x 10

Bug Score Mitigation Action
Score <= 10 Use buffer time to fix.
10 < Score <= 20 Use planned debugging time in the iteration to carry out bug fix
Score > 20 Stop current development and resolve the bug immediately. Project Manager to reschedule the project.