IS480 Team wiki: 2014T1 Team Epsilon Metrics Management
Home | Project Overview | Project Management | Documentation | Team |
Methodology | Project Schedule | Metrics Management | Risk Management |
Schedule Metrics
Absolute Days Delayed
If stories cannot be completed on time, they will either be:
- scheduled to be done in the next iteration (timebox) OR
- be developed by extending the current iteration
The decision will be based on the progress of the story as well as if there are any milestones that need to be met.
Schedule Index Guide
Schedule Index
Bug Metrics
Severity | Description |
---|---|
Low Impact (1 point) |
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. |
Bug Points* | Action |
---|---|
< 10 | Use the planned debugging time in the iteration. |
>= 10 | Stop current development and resolve the bugs immediately. Project Manager reschedules the project. |
* Bug Points = (# Low Impact Bugs) + 5(# High Impact Bugs) + 10(# Critical Impact Bugs)
Change Metrics
Effort Metrics
Task | Weightage |
---|---|
Technical | 2 |
Project Management | 1.5 |
Other | 1 |
Effort Valuation = [ 2(# Technical Tasks) + 1.5(# Project Management Tasks) + (Other Tasks) ] ÷ [ Total # Tasks In Iteration ]