Difference between revisions of "IS480 Team wiki: 2016T2 LOCK Project Metrics"
Jump to navigation
Jump to search
Mitigation Plan (Bug Metrics)
Mitigation Plan (Client Metrics)
(33 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
+ | <!--Logo--> | ||
+ | [[Image:LockLogo3.jpg|left|150px]]<br> | ||
+ | |||
<!--MAIN HEADER --> | <!--MAIN HEADER --> | ||
− | {|style="background-color:#ffffff ; color:#ffffff; padding: 5 0 5 0;" width="100%" cellspacing=" | + | {|style="background-color:#ffffff ; color:#ffffff; padding: 5 0 5 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" | |
+ | |||
+ | | style="padding:0.1em; font-size:100%; background-color:#000000; text-align:center; color:#ffffff" width="10%" | [[Image: LockHouse.png|18x18px|sub|link=]] [[IS480_Team_wiki:_2016T2_LOCK | <font color="#ffffff" size=2 face="Arial">HOME</font>]] | ||
+ | |||
+ | | style="padding:0.1em; font-size:100%; background-color:#000000; text-align:center; color:#ffffff" width="10%" | [[Image: LOCK-About Us.png|30x30px|middle|link=]] [[IS480_Team_wiki:_2016T2_LOCK_AboutUs | <font color="#ffffff" size=2 face="Arial">ABOUT US</font>]] | ||
+ | |||
+ | | style="padding:0.1em; font-size:100%; background-color:#000000; text-align:center; color:#ffffff" width="10%" |[[Image: lockGraph.png|18x18px|sub|link=]] [[IS480_Team_wiki:_2016T2_LOCK_ProjectOverview | <font color="#ffffff" size=2 face="Arial">PROJECT OVERVIEW</font>]] | ||
+ | |||
+ | | style="padding:0.6em; font-size:100%; background-color:#aa1d23; text-align:center; color:#ffffff" width="10%" | [[Image:lockManage.png|20px|link=]] [[IS480_Team_wiki:_2016T2_LOCK_Project | <font color="#ffffff" size=2 face="Arial"><b>PROJECT MANAGEMENT</b></font>]] | ||
+ | |||
+ | | style="padding:0.1em; font-size:100%; background-color:#000000; text-align:center; color:#ffffff" width="10%" | [[Image: lockDocuments.png|18x18px|sub|link=]][[IS480_Team_wiki:_2016T2_LOCK_Documentation | <font color="#ffffff" size=2 face="Arial">DOCUMENTATION</font>]] | ||
+ | |} | ||
+ | |||
+ | <!--Sub Header Start--> | ||
+ | | ||
+ | {| class="wikitable;style="background-color:white; color:white padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" | ||
+ | |- | ||
+ | | style="vertical-align:top;width:25%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; font-size:16px; border-bottom:1px font-family:Arial">[[IS480_Team_wiki:_2016T2_LOCK_Project | <font color="#000000"><b>Project Schedule</b></font>]] || style="vertical-align:top;width:25%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; font-size:16px; border-bottom:3px solid #aa1d23; font-family:Arial"> [[IS480_Team_wiki:_2016T2_LOCK_Project_Metrics | <font color="#aa1d23"><b>Metrics</b></font>]] || style="vertical-align:top;width:25%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; font-size:16px; border-bottom:1px font-family:Arial"> [[IS480_Team_wiki:_2016T2_LOCK_Project_RiskAssessment | <font color="#000000"><b>Risk Assessment</b></font>]]|| style="vertical-align:top;width:25%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; font-size:16px; border-bottom:1px font-family:Arial">[[IS480_Team_wiki:_2016T2_LOCK_Project_ChangeManagement | <font color="#000000"><b>Change Management</b></font>]] | ||
+ | |} | ||
− | + | <!--Sub Header End--> | |
− | | style=" | + | <!-- Schedule Matrix--> |
+ | [[Image:TeamLockScheduleWords.png|center|350px]] | ||
+ | ==<b>Schedule Tracking Category</b>== | ||
+ | {| class="wikitable" | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | Score(%) | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | 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 | ||
+ | |} | ||
− | | style=" | + | ==<b>SM Score = Estimated No. of Days in Iteration / Actual No. of Days spent in Iteration</b>== |
+ | {| class="wikitable" | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | Score(%) | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | 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. | ||
+ | |} | ||
− | + | [[Image:TeamLockSchdMetrics.png|center|1000px]] | |
− | | style=" | + | <br/> |
+ | [[Image:TeamLockBugWords.png|center|350px]] | ||
+ | <!-- Bug Metrics --> | ||
+ | |||
+ | ==<b>Impact Score (Bug Metrics)</b>== | ||
+ | {| class="wikitable" | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | Severity | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | 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 | ||
|} | |} | ||
− | |||
− | |||
− | | style=" | + | ==<b>Mitigation Plan (Bug Metrics)</b><br/>== |
− | + | Total Score = # Bugs (Low) x 1 + # Bugs (High) x 5 + # Bugs (Critical) x 10 | |
+ | {| class="wikitable" | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | Bug Score | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | 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. | ||
+ | |} | ||
− | + | <br/> | |
− | [[ | + | [[File:Ios Bug Metrics.PNG|center|900px]] |
+ | <br/> | ||
+ | [[File:Android_bug_Metrics.PNG|center|900px]] | ||
− | | style=" | + | <!-- Client Metrics --> |
− | + | <br/> | |
+ | [[Image:ClientMetricsWord.png|center|350px]] | ||
+ | ==<b>Impact Score (Client Metrics)</b>== | ||
+ | {| class="wikitable" | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | Client Score | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | Description | ||
+ | |- | ||
+ | | CM <= 0.5 | ||
+ | | Bad | ||
+ | |- | ||
+ | | 0.5 < CM <= 0.7 | ||
+ | | Average | ||
+ | |- | ||
+ | | 0.7 < CM <= 0.9 | ||
+ | | Good | ||
+ | |- | ||
+ | | 0.9 < CM <= 1 | ||
+ | | Exceptional | ||
+ | |} | ||
− | | style=" | + | ==<b>Mitigation Plan (Client Metrics)</b><br/>== |
− | + | Total Score = Score/10 | |
+ | {| class="wikitable" | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | Client Score | ||
+ | ! style="font-weight: bold;background: #aa1d23;color:#fff;" | Mitigation Action | ||
+ | |- | ||
+ | | CM <= 0.5 | ||
+ | | Clients are not pleased at our work. Halt all tasks and review with both clients and team on what went wrong. Priorities would be placed on making the right changes | ||
+ | |- | ||
+ | | 0.5 < CM <= 0.7 | ||
+ | | Clients are relatively less pleased with our work. Discuss with client and team on how to improve our score for the next week | ||
+ | |- | ||
+ | | 0.7 < CM <= 0.9 | ||
+ | | Clients are pleased with our work so far. Continue on the same path and discuss with team on how to get a higher rating for the next week | ||
+ | |- | ||
+ | | 0.9 < CM <= 1 | ||
+ | | Clients are more than pleased with our work. Continue on the same path and PM to make sure that team doesnt get complacent | ||
|} | |} | ||
− | [[Image: | + | <br/> |
+ | [[Image:TeamLockClientMetrics.png|center|900px]] |
Latest revision as of 00:08, 19 April 2016
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Contents
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. |
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. |
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 |
---|---|
CM <= 0.5 | Clients are not pleased at our work. Halt all tasks and review with both clients and team on what went wrong. Priorities would be placed on making the right changes |
0.5 < CM <= 0.7 | Clients are relatively less pleased with our work. Discuss with client and team on how to improve our score for the next week |
0.7 < CM <= 0.9 | Clients are pleased with our work so far. Continue on the same path and discuss with team on how to get a higher rating for the next week |
0.9 < CM <= 1 | Clients are more than pleased with our work. Continue on the same path and PM to make sure that team doesnt get complacent |