HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 107: Line 107:
  
 
<br/>
 
<br/>
[[Image:TeamLockBugAndroid.png|center|9000px]]
+
[[Image:TeamLockBugAndroid.png|center|900px]]
 
<br/>
 
<br/>
[[Image:TeamLockBugIOS.png|center|9000px]]
+
[[Image:TeamLockBugIOS.png|center|900px]]

Revision as of 15:00, 19 February 2016

LockLogo3.jpg


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

 


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 and client about the slip within 24 hours. Using the same action for 50 < SM <= 90, consider dropping functionalities.
50 < SM <= 90 PM to discuss with team and re-estimate for future iterations. Eat into buffer days if any change is needed. Analyze the cause of delay and make necessary corrections.
90 < SM <= 110 Estimates are fairy accurate and we are roughly on track. Consider adding remaining days into buffer date or deducting buffer days to cater for changes.
110 < SM <= 150 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 and client about the slip within 24 hours. Using the same action for 110 < SM <= 150, consider adding functionalities.
TeamLockSchdMetrics.png


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.


TeamLockBugAndroid.png


TeamLockBugIOS.png