IS480 Team wiki: 2016T1 Stark Project Management Metrics
Revision as of 13:08, 18 November 2016 by Cylee.2013 (talk | contribs)
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.
|
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.
|
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 |