Difference between revisions of "IS480 Team wiki: 2012T1 Shopaholic Project Management Metrices"
Jump to navigation
Jump to search
Mei.zou.2010 (talk | contribs) |
Mei.zou.2010 (talk | contribs) |
||
Line 234: | Line 234: | ||
! width="250" style="border: 1px solid black; background: #474747; padding: 5px;"| <font color="#ffffff">Corrective Actions</font> | ! width="250" style="border: 1px solid black; background: #474747; padding: 5px;"| <font color="#ffffff">Corrective Actions</font> | ||
|- | |- | ||
− | |style="border: 1px solid black; text-align: center; padding: 10px;"|<font color="#474747"><15</font> | + | |style="border: 1px solid black; text-align: center; padding: 10px;"|<font color="#474747"><b><15</b></font> |
|style="border: 1px solid black; text-align: center; padding: 10px;"|<font color="#474747">Low</font> | |style="border: 1px solid black; text-align: center; padding: 10px;"|<font color="#474747">Low</font> | ||
|style="border: 1px solid black; padding: 10px;"|<font color="#474747">To resolve immediately for those bugs that will cause malfunctions, minor bugs to be resolved during scheduled bug fix time for the iteration</font> | |style="border: 1px solid black; padding: 10px;"|<font color="#474747">To resolve immediately for those bugs that will cause malfunctions, minor bugs to be resolved during scheduled bug fix time for the iteration</font> |
Revision as of 13:40, 20 September 2012
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 July 2012 | 31 July 2012 | 13 days | 19 July 2012 | 02 August 2012 | 15 days | 2 days | 1.15 | Used 2 Buffered days |
2. | 03 August 2012 | 10 August 2012 | 8 days | 03 August 2012 | 10 August 2012 | 8 days | - | 1 | Nil |
3. | 13 August 2012 | 24 August 2012 | 12 days | 13 August 2012 | 26 August 2012 | 14 days | 2 days | 1.16 | Used 2 Buffered days |
4. | 27 August 2012 | 12 September 2012 | 17 days | 27 August 2012 | 15 September | 20 days | 3 days | 1.17 | Used 3 Buffered days |
5. | 16 September 2012 | 28 September 2012 | 13 days | ||||||
6. | 01 October 2012 | 12 October 2012 | 12 days | ||||||
7. | 15 October 2012 | 19 October 2012 | 5 days | ||||||
8. | 22 October 2012 | 2 November 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 | |
5 | Normal | Moderate | |
10 | Major | Difficult |
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 |