IS480 Team wiki: 2012T1 Shopaholic Project Management Metrices
Our Team | Project Overview | Project Management | Development | Learning Outcome | Documentation |
| | | | Metrices | | | Risk & Mitigation | | |
Contents
Metrices
Schedule Metric
Iteration | Planned Start Date (PSD) |
Planned End Date (PED) |
Planned Duration(PD): (PED)-(PSD) |
Actual Start Date (ASD) |
Actual End Date (AED) |
Actual Duration(AD): (AED)-(ASD) |
Duration Difference: (AD)-(PD) |
Performance Index |
Progress Remarks |
---|---|---|---|---|---|---|---|---|---|
1. | 19 Jul 2012 | 31 Jul 2012 | 13 days | 19 Jul 2012 | 02 Aug 2012 | 15 days | 2 days | 1.15 | Used 2 Buffered days |
2. | 03 Aug 2012 | 10 Aug 2012 | 8 days | 03 Aug 2012 | 10 Aug 2012 | 8 days | - | 1 | Nil |
3. | 13 Aug 2012 | 24 Aug 2012 | 12 days | 13 Aug 2012 | 26 Aug 2012 | 14 days | 2 days | 1.16 | Used 2 Buffered days |
4. | 27 Aug 2012 | 12 Sep 2012 | 17 days | 27 Aug 2012 | 15 Sep 2012 | 20 days | 3 days | 1.17 | Used 3 Buffered days |
5. | 16 Sep 2012 | 28 Sept 2012 | 13 days | 16 Sep 2012 | 30 Sep 2012 | 15 days | 2 days | Extended 10 days / Behind Progress | |
6. | 15 Oct 2012 | 26 Oct 2012 | 12 days | ||||||
7. | 29 Oct 2012 | 4 Nov 2012 | 5 days | ||||||
8. | 5 Nov 2012 | 16 Nov 2012 | 12 days |
Performance Index & Corrective Actions
Schedule Performance Index (SPI) = Actual Duration ÷ Planned Duration
Project Progress | SPI Ratio | Corrective Actions |
---|---|---|
Extremely Ahead of Schedule | <0.6 | Proceed to the next iteration. |
Ahead of Schedule | <1 | Based on the severity of the ratio, Project Manager to decide whether to proceed to the next iteration. To hold team meetings for discussion on severe cases. |
On Schedule | 1 - 1.2 | The team is to continue working as planned by the schedule in the next iteration |
Behind Schedule | >1.2 | PM & Lead Developer to initiate discussions prior to decide for whether to hold team meetings To either drop functionalities or extend the current iteration. |
Extremely Behind Schedule | >1.4 | Drop current functionalities and move to the next iteration. |
Bug Metric
Bug Metric Formula: Sum of Bug Points for the iteration
Bug Point Allocation System | |||
---|---|---|---|
Bug Points | Bug Type | Complexity | Description |
1 | Minor | Easy | Minor cosmetic bugs, bugs that is sure to need less time for fixing |
5 | Normal | Moderate | Bugs that requires more time to fix and there is solution to the fixing of the bugs |
10 | Major | Difficult | Major bugs that will affect the development of the site and hinders the functionality of the current functions |
Corrective Actions
Total Bug Points | Risk Level | Corrective Actions |
---|---|---|
<15 | Low | To resolve immediately for those bugs that will cause malfunctions, minor bugs to be resolved during scheduled bug fix time for the iteration |
15 ~ 50 | Medium | Lead developer to schedule meeting with developers to discuss mitigation plans for solving the bugs |
>50 | High | Project Manager to schedule team meeting to discuss action plans. Team plan for a bug fix day and pause all current coding developments |