IS480 Team wiki: 2015T1 A3XY ScheduleMetrics
Revision as of 13:50, 22 November 2015 by Poojat.2012 (talk | contribs)
Project Schedule | Schedule Metrics | Bug Metrics | Risk Management | Change Management |
|
Iteration | Completion % | Planned Days | Actual Days | Metric Index |
---|---|---|---|---|
1 | 100% | 14 | 16 | 0.88 |
2 | 100% | 14 | 15 | 0.93 |
3 | 100% | 14 | 14 | 1.00 |
4 | 100% | 14 | 17 | 0.82 |
5 | 100% | 14 | 9 | 1.56 |
6 | 100% | 14 | 17 | 0.82 |
7 | 100% | 14 | 15 | 0.93 |
8 | 100% | 14 | 10 | 1.40 |
9 | 100% | 9 | 9 | 1.00 |
10 | 100% | 14 | 19 | 0.74 |
11 | 100% | 15 | 15 | 1.00 |
Documentation
SM < 50 | 1.Immediately, inform your supervisor about the slip within 24 hours.
2.Then use the same mitigation as the category 50 < SM < 90 and seriously consider dropping tasks. |
50 < SM <= 90 | 1.Re-estimate the tasks for the 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. |
90 < SM <= 110 | Our estimates are fairly accurate, and we are roughly on track.
1.Add/Deduct the number of days behind schedule from buffer days. |
110 < SM <= 150 | Gross over-estimated the effort required.
1.Re-estimate the tasks for the future iterations 2.Add the number of days gained to buffer days |
150 < SM | 1.Immediately inform PM about the slip within 24 hours
2.Then use the mitigation as the category 110 < SM <= 150 |