HeaderSIS.jpg

IS480 Team wiki: 2016T1 Stark Project Management Metrics

From IS480
Jump to navigation Jump to search
Team Stark Logo.png


Team Stark Home.png   HOME

 

Team Stark About Us.png   ABOUT US

 

Team Stark Project Overview.png   PROJECT OVERVIEW

 

Team Stark Project Management.png   PROJECT MANAGEMENT

 

Team Stark Documentation.png   DOCUMENTATION

 


SCHEDULE METRICS BUG METRICS
Schedule Metrics


What: Schedule metrics are used to measure the progress of project.
When: It is measured at the end of each iteration.
How: Planned number of days/Actual number of days

Score Action
SM <= 0.9 Team is behind the schedule. Effort required to complete is under-estimated.
  1. Inform Supervisor
  2. Re-estimate tasks for future iterations
  3. Deduct the number of days behind schedule from buffer days
  4. If there is no more buffer day, decide the functionalities to drop
0.9 < SM <= 1.1 Estimates are fairly accurate and team is on schedule.
SM > 1.1 Team is ahead of schedule. Effort required to complete is over-estimated.
  1. Inform Supervisor
  2. Re-estimate tasks for future iterations
  3. Add the number of days gained to buffer days


Stark SM.png


Iteration Planned Duration (Days) Actual Duration (Days) Schedule Metric Score Action Taken Status
8 14 16 0.88 More time needed to fix bugs from UT1 and after the integration of Dispute Management.

Follow up action: Informed supervisor and mentor about the delay. More hours put in for debugging. No major delay to overall schedule.

Completed
13 14 16 0.88 Underestimated the complexity of 'Web Push Notification'

Follow up action: Informed supervisor and mentor about the delay. No major delay to overall schedule.

Completed