HeaderSIS.jpg

IS480 Team wiki: 2016T2 LickiLicky Task Metrics

From IS480
Jump to navigation Jump to search

LickiLicky Logo v2.png

HOME   ABOUT US   PROJECT OVERVIEW   PROJECT MANAGEMENT   DOCUMENTATION
Project Timeline Metrics Risks Change Management
SCHEDULE METRICS TASK METRICS BUG METRICS
Task Metrics


What: Task metrics are used to measure the team's progress when completing tasks.
When: It is measured at the end of each task.
How: Planned number of hours/Actual number of hours

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

Task Metrics Chart

Task Metrics.png


Iteration Task Score Description Action Taken
9 0.87 Underestimated the hours needed to develop link contact (0.67) Underestimated the hours needed for debugging (0.6) Underestimated the hours needed to analyse user test result (0.5) Allocate more hours for future development tasks with similar level of complexity.

Allocate more hours to analyse user test result for future user test.






Archived Task Metrics