HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 75: Line 75:
 
<!-- Bug Metrics -->
 
<!-- Bug Metrics -->
  
==<b>Impact Score</b>==
+
==<b>Impact Score (Bug Metrics)</b>==
 
{| class="wikitable"
 
{| class="wikitable"
 
! style="font-weight: bold;background: #aa1d23;color:#fff;" | Severity
 
! style="font-weight: bold;background: #aa1d23;color:#fff;" | Severity
Line 90: Line 90:
 
|}
 
|}
  
==<b>Mitigation Plan</b><br/>==
+
==<b>Mitigation Plan (Bug Metrics)</b><br/>==
 
Total Score = # Bugs (Low) x 1 + # Bugs (High) x 5 + # Bugs (Critical) x 10
 
Total Score = # Bugs (Low) x 1 + # Bugs (High) x 5 + # Bugs (Critical) x 10
 
{| class="wikitable"
 
{| class="wikitable"
Line 114: Line 114:
 
<br/>
 
<br/>
 
[[Image:ClientMetricsWord.png|center|350px]]
 
[[Image:ClientMetricsWord.png|center|350px]]
==<b>Impact Score</b>==
+
==<b>Impact Score (Client Metrics)</b>==
 
{| class="wikitable"
 
{| class="wikitable"
! style="font-weight: bold;background: #aa1d23;color:#fff;" | Severity
+
! style="font-weight: bold;background: #aa1d23;color:#fff;" | Client Score
 
! style="font-weight: bold;background: #aa1d23;color:#fff;" | Description
 
! style="font-weight: bold;background: #aa1d23;color:#fff;" | Description
 
|-
 
|-
| Low Impact (1 - 4 points)
+
| CM <= 0.5
| Inconsequential. Simple typo error or minor user interface misalignment.
+
| Bad
 +
|-
 +
| 0.5 < CM <= 0.7
 +
| Average
 
|-
 
|-
| High Impact (5 - 9 points)
+
| 0.7 < CM <= 0.9
| The system runs. However, some non-critical functionalities are not working
+
| Good
 
|-
 
|-
| Critical Impact (10 points)
+
| 0.9 < CM <= 1
| The system is down or is unstable after a short period of time. Bug fix immediately to continue
+
| Exceptional
 
|}
 
|}
  
==<b>Mitigation Plan</b><br/>==
+
==<b>Mitigation Plan (Client Metrics)</b><br/>==
 
Total Score = Score/10
 
Total Score = Score/10
 
{| class="wikitable"
 
{| class="wikitable"

Revision as of 15:12, 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 (Bug Metrics)

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 (Bug Metrics)

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


ClientMetricsWord.png

Impact Score (Client Metrics)

Client Score Description
CM <= 0.5 Bad
0.5 < CM <= 0.7 Average
0.7 < CM <= 0.9 Good
0.9 < CM <= 1 Exceptional

Mitigation Plan (Client Metrics)

Total Score = Score/10

Client 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.


TeamLockClientMetrics.png