IS480 Team wiki: 2013T2 D'PENZ Metrics Management
Jump to navigation
Jump to search
Home | Our Team | Project Overview | Project Management | Project Documentation |
Methodology | Project Schedule | Metrics Management | Risk & Change Management |
Contents
Schedule Metrics
Absolute Days Delayed
Percentage
Effort Metrics
Bug Metrics
Bug Tracker Guide
Severity | Description |
---|---|
Low Impact (1 points) | Unimportant. Typo error or small user interface alignment issues. |
High Impact (5 points) | The system runs. However, some non-critical functionalities are not working. |
Critical Impact(10 points) | The system is down or is un-usable after a short period of time. We have to fix the bugs to continue |
Points in Iteration | Action |
---|---|
Points < 10 | Use the planned debugging time in the iteration. |
Points >= 10 | Stop current development and resolve bugs immediately. Project Manager reschedules the project. |
Test Results
Sprint | Bug Value | Documents |
---|---|---|
3 | 4 (Bug solved in planned debugging time) |
Test Cases , Bug Tracker |
4 | 11 (Halt progress and resolve bugs) |
Test Cases , Bug Tracker |
5 | 25 (Halt progress and resolve bugs) |
Test Cases , Bug Tracker |
6 | 12 (Halt progress and resolve bugs **Note: bugs solved in planned debugging time due to high number of low priority bugs) |
Test Cases , Bug Tracker |
7 | 14 (Resolve bugs immediately) |
Test Cases , Bug Tracker |
8 | 29 (Resolve bugs immediately) |
Test Cases , Bug Tracker |
9 | 8 (Solve bugs within planned debugging time) |
Test Cases , Bug Tracker |