IS480 Team wiki: 2017T2 CAVETZ Project Management Metrics
Jump to navigation
Jump to search
SCHEDULE METRICS | BUG METRICS | EFFORT METRICS |
---|
Schedule Metrics
Schedule metrics are used to measure the progress of project. The metrics is measure at the end of each iteration by using this formula:
Actual number of days - Planned number of days
S/N | SM Score | Action To Take |
---|---|---|
1. | SM < -5 | 1. Hold urgent meeting and inform supervisor immediately if necessary. 2. Then use the same mitigation as category 0.5 < SM <= 0.9 and seriously consider dropping tasks. |
2. | -3 <= SM <= -5 | 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. | -3 < SM < 3 | Estimates are fairly accurate and team is on schedule. No actions need to be taken. |
4. | 3 <= SM <= 5 | 1. Re-estimate the tasks for future iterations. 2. Add the number of days gained to buffer days. |
5. | 5 < SM | 1. Hold a meeting to decide necessity of additional testing. Inform supervisor if necessary. 2. Then use the same mitigation as category 1.1 < SM <= 1.5. |
The table below shows the details of iteration that has SM >= 3 or SM <= -3
Iteration | Planned Duration (Days) | Actual Duration (Days) | Schedule Metric Score | Action Taken | Status | |
---|---|---|---|---|---|---|
4 | 32 | 35 | 3 | Underestimated time needed to fix bugs in deployment environment.
Follow up action: Informed the course coordinator about the delay. More hours put in for debugging. PM to push spreadsheet function to iteration 10 as a good-to-have function after discussion with sponsor. No major delay to overall schedule. |
Completed |