HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 Charlies Angels Metrics"

From IS480
Jump to navigation Jump to search
Line 44: Line 44:
 
|}  
 
|}  
 
<!--CONTENT-->
 
<!--CONTENT-->
<div style="margin-top:20px">
+
<div style="margin-top:20px; margin-bottom:10px;">
 
[[Image:Charlies-Angels-Metrics.png|center|1000px|link=]]
 
[[Image:Charlies-Angels-Metrics.png|center|1000px|link=]]
 
</div>
 
</div>
 +
 +
<!--CONTENT-->
 +
<div style="width:70%; background: #000000; margin-top:10px; margin-left:10%; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>Schedule Metrics</font></div>
 +
{| class="wikitable" style="background-color:#FFFFFF; width:73%;margin-left:10%; text-align: center;"
 +
|-
 +
! style="color:white; background-color:#000000;" | S/N
 +
! style="color:white; background-color:#000000;" | SM Score
 +
! style="color:white; background-color:#000000;" | Action To Take
 +
|-
 +
| 1.
 +
| SM < 50
 +
| 1. Immediately, inform supervisor about the slip within 24 hours.<br/>2. Then use the same mitigation as category 50 < SM <= 90<br/>and seriously consider dropping tasks.
 +
|-
 +
| 2.
 +
| 50 < SM <= 90
 +
| 1. Re-estimate the tasks for future iterations.<br/>2. Deduct the number of days behind schedule from buffer days.<br/>3. If there is no more buffer days, decide on functionalities to drop.
 +
|-
 +
| 3.
 +
| 90 < SM <= 110
 +
| 1. Add/Deduct the number of days behind schedule from buffer days.<br/>2. If there is no more buffer days, decide the functionalities to drop.
 +
|-
 +
| 4.
 +
| 110 < SM <= 150
 +
| 1. Re-estimate the tasks for future iterations.<br/>2. Add the number of days gained to buffer days.
 +
|-
 +
| 5.
 +
| 150 < SM
 +
| 1. Immediately, inform supervisor about the slip within 24 hours.<br/>2. Then use the same mitigation as category 110 < SM <= 150.
 +
|-
 +
|-
 +
 +
|}
 +
 +
<div style="width:70%; background: #7f0000; margin-top:10px; margin-left:10%; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>Bug Metrics</font></div>
 +
{| class="wikitable" style="background-color:#FFFFFF; width:73%;margin-left:10%;margin-top:10px; text-align: center;"
 +
|-
 +
! style="color:white; background-color:#7f0000;" | S/N
 +
! style="color:white; background-color:#7f0000;" | BM Score
 +
! style="color:white; background-color:#7f0000;" | Action To Take
 +
|-
 +
| 1.
 +
| Points < 10
 +
| 1. Use the planned debugging time in iteration to resolve.
 +
|-
 +
| 2.
 +
| Points >= 10
 +
| 1. Stop current development and resolve the bug immediately.<br/>2. Project Manager reschedules the project.
 +
|-
 +
|}
 +
<div style="width:70%; background: #ffd700; margin-top:10px; margin-left:10%; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>Client Satisfaction Metrics</font></div>
 +
{| class="wikitable" style="background-color:#FFFFFF; width:73%;margin-left:10%;margin-top:10px; text-align: center;"
 +
|-
 +
! style="color:white; background-color:#ffd700;" | S/N
 +
! style="color:white; background-color:#ffd700;" | CSM Score
 +
! style="color:white; background-color:#ffd700;" | Action To Take
 +
|-
 +
| 1.
 +
| 0 <= CSM < 5
 +
| 1. Stop development and hold an urgent meeting with our client to understand<br/>and resolve the concerns or misunderstandings we have.
 +
|-
 +
| 2.
 +
| 5 <= CSM < 7
 +
| 1. Project Manager has to better manage the client with taste response time<br/>and minimal miscommunication.<br/>2. Project Manager has to constantly check with the client to see if<br/>the team is producing what the client requests for.
 +
|-
 +
| 3.
 +
| 7 <= CSM <= 10
 +
| 1. Continue to work hand-in-hand with our client and<br/>achieve the results that have been aimed for.
 +
|-
 +
|}
 +
<div style="width:70%; background: #228b22; margin-top:10px; margin-left:10%; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>Team Enthusiasm Metrics</font></div>
 +
{| class="wikitable" style="background-color:#FFFFFF; width:73%;margin-left:10%;margin-top:10px; text-align: center;"
 +
|-
 +
! style="color:white; background-color:#228b22;" | S/N
 +
! style="color:white; background-color:#228b22;" | TEM Score
 +
! style="color:white; background-color:#228b22;" | Action To Take
 +
|-
 +
| 1.
 +
| 0 <= TEM < 5
 +
| 1. Stop development and hold an urgent meeting within the team to understand<br/>and resolve the concerns or misunderstandings we have amongst each other.
 +
|-
 +
| 2.
 +
| 5 <= TEM < 7
 +
| 1. Project Manager has to constantly check each team member to see if they are<br/>enjoying what they are doing, and to observe for any problems they<br/>might be facing either with the project or members.
 +
|-
 +
| 3.
 +
| 7 <= TEM <= 10
 +
| 1. Continue encouraging one another to work hard<br/>and enjoy the project together.
 +
|-
 +
|}

Revision as of 01:10, 8 July 2016


Charlies Angels Logo.png


Charlies Angels Home.png  HOME

 

Charlies Angels About Us.png  ABOUT US

 

Charlies Angels Project Overview.png  PROJECT OVERVIEW

 

Charlies Angels Project Management.png  PROJECT MANAGEMENT

 

Charlies Angels Project Documentation.png  DOCUMENTATION

 
Project Schedule Risk Management Charlies Angels Current Stage.png Metrics
Charlies-Angels-Metrics.png
Schedule Metrics
S/N SM Score Action To Take
1. SM < 50 1. Immediately, inform supervisor about the slip within 24 hours.
2. Then use the same mitigation as category 50 < SM <= 90
and seriously consider dropping tasks.
2. 50 < SM <= 90 1. Re-estimate the tasks for future iterations.
2. Deduct the number of days behind schedule from buffer days.
3. If there is no more buffer days, decide on functionalities to drop.
3. 90 < SM <= 110 1. Add/Deduct the number of days behind schedule from buffer days.
2. If there is no more buffer days, decide the functionalities to drop.
4. 110 < SM <= 150 1. Re-estimate the tasks for future iterations.
2. Add the number of days gained to buffer days.
5. 150 < SM 1. Immediately, inform supervisor about the slip within 24 hours.
2. Then use the same mitigation as category 110 < SM <= 150.
Bug Metrics
S/N BM Score Action To Take
1. Points < 10 1. Use the planned debugging time in iteration to resolve.
2. Points >= 10 1. Stop current development and resolve the bug immediately.
2. Project Manager reschedules the project.
Client Satisfaction Metrics
S/N CSM Score Action To Take
1. 0 <= CSM < 5 1. Stop development and hold an urgent meeting with our client to understand
and resolve the concerns or misunderstandings we have.
2. 5 <= CSM < 7 1. Project Manager has to better manage the client with taste response time
and minimal miscommunication.
2. Project Manager has to constantly check with the client to see if
the team is producing what the client requests for.
3. 7 <= CSM <= 10 1. Continue to work hand-in-hand with our client and
achieve the results that have been aimed for.
Team Enthusiasm Metrics
S/N TEM Score Action To Take
1. 0 <= TEM < 5 1. Stop development and hold an urgent meeting within the team to understand
and resolve the concerns or misunderstandings we have amongst each other.
2. 5 <= TEM < 7 1. Project Manager has to constantly check each team member to see if they are
enjoying what they are doing, and to observe for any problems they
might be facing either with the project or members.
3. 7 <= TEM <= 10 1. Continue encouraging one another to work hard
and enjoy the project together.