HeaderSIS.jpg

IS480 Team wiki: 2012T1 Shopaholic Project Management Metrices

From IS480
Jump to navigation Jump to search
TeamShopaholic.png
Our Team   Project Overview   Project Management   Development   Learning Outcome   Documentation


|

Schedule

| Metrices | Risk & Mitigation |


Metrices

500px 377px

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 1.15 Extended 10 days / Behind Progress
6. 15 Oct 2012 2 Nov 2012 19 days 15 Oct 2012 3 Nov 2012 20 days 1 day 1.05 Used 1 Buffered day
7. 5 Nov 2012 16 Nov 2012 12 days 5 Nov 2012 17 Nov 2012 13 days 1 day 1.05 Used 1 Buffered day
8. 18 Nov 2012 29 Nov 2012 12 days 18 Nov 2012 29 Nov 2012 12 days - 1 Nil


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 Points Overview Overall.jpg Bug Count Overview Overall.jpg

  Bug Count by Complexity    
Iteration Minor Normal Major Total Bug Count Total Bug Points
1 0 0 0 0 0
2 0 2 0 2 10
3 2 1 1 4 17
4 11 7 1 19 56
5 9 7 0 16 35
6 15 6 0 21 45
7 3 2 0 5 13
8 19 5 0 24 44


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