HeaderSIS.jpg

IS480 Team wiki: 2016T1 Charlies Angels Metrics

From IS480
Jump to navigation Jump to search


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 Change Management Charlies Angels Current Stage.png Metrics
Charlies-Angels-Metrics.png
Schedule Metrics

Schedule Metrics Score = Planned # of Days / Actual # of Days

S/N SM Score Action To Take
1. SM < 0.5 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. 0.5 < SM <= 0.9 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. 0.9 < SM <= 1.1 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. 1.1 < SM <= 1.5 1. Re-estimate the tasks for future iterations.
2. Add the number of days gained to buffer days.
5. 1.5 < SM 1. Immediately, inform supervisor about the slip within 24 hours.
2. Then use the same mitigation as category 110 < SM <= 150.
Bug Metrics

Bug Metrics Score = Bug score at the end of the iteration. 1 point for Low Impact, 5 points for High Impact,
10 points for Critical Impact bugs to the project

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

Client Satisfaction Metrics Score = Average of the sum of the score for each of the following questions:
Rate the following from 1 to 10, with 10 being the highest.
a) How satisfied are you with the application’s ease of use?
b) How satisfied are you with the look and feel of this application?
c) How well does our application meet your needs?
d) How would you rate the quality of the product?
e) Overall, I am very satisfied with the way the team is performing on this project.
f) How responsive has the team been to your questions or concerns about the application?
g) Any other comments?

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

Team Enthusiasm Metrics Score = Average of all team member’s score for the following questions:
Rate the following from 1 to 10, with 10 being the highest.
a) Are you happy working with your team members?
b) Do you feel motivated to move on to the next iteration?
c) Are you happy with the progress your team has so far?
d) Overall, how effectively did your team work together this iteration?
e) How high do you think your team morale is?

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.