IS480 Team wiki: 2016T2 LickiLicky Metrics
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Project Timeline | Metrics | Risks | Change Management |
---|
SCHEDULE METRICS | TASK METRICS | BUG 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.
|
Schedule Metrics Table
Iteration | Planned Duration (Days) | Actual Duration (Days) | Schedule Metric Score | Action Taken | Status |
---|---|---|---|---|---|
3 | 14 | 16 | 0.88 | More time needed to complete suggest group function. Follow up action: Schedule slip was presented during Acceptance presentation. No delay to overall schedule as there are no major function to be developed in Iteration 4, which was scheduled to be preparation for Acceptance. Supervisor was informed of the slip after project was Accepted. |
Completed |
7 | 14 | 16 | 0.88 | More time needed to develop filter search function. Follow up action: Supervisor informed about delay. More hours was put into developing the function. No major delay in overall schedule as PM scheduled only one function, birthday reminder, to be developed in Iteration 8 due to festive period. |
Completed |
11 | 14 | 17 | 0.82 | More time needed to develop Hashtags. Follow up action: Supervisor informed about delay. More hours was put into developing the function. No major delay in overall schedule. |
Completed |