2013T2 golf.(y).peer Metrics
Jump to navigation
Jump to search
Home | Team Description | Project Overview | Project Management | Project Documentation | Project Resources | Team Reflection |
---|
Project Schedule | Framework | Metrics | Risk Management | Minutes & Status Reports |
Schedule Metric
- Keeps track of project progress
- Monitored per Iteration
- Formula: Planned Days / Actual Days
Score(%) | Description | Action |
SM < 50 | Team is way behind schedule |
|
50<SM<=90 | Team is behind schedule |
|
90<SM<=110 | Team is on track |
|
110<SM<=150 | Team is ahead of schedule |
|
150 < SM | Team is way ahead of schedule |
|
Bug Metric
- Helps in prioritizing bug solving time
- Monitored per Iteration
- Formula: 1 X number of low bugs + 5 X number of medium bugs + 10 X number of critical bugs
Severity | Bug Point | Bug Description |
Low Impact | 1 | Only minor aesthetic changes are to be made; does not affect system's operational requirements |
High Impact | 5 points | Causes some non-critical functionalities to be non-operational, but system is still capable to run overall |
Critical Impact | 10 points | Causes the system to be non-operational. System will only work after bugs are resolved |
Total bug points | Action |
Bug points <= 5 | Fix during buffer time only |
5 < Bug point < 15 | Use the planned debugging/testing time |
Bug point >= 15 | Stop current development and resolve the bug immediately. Project Manager reschedules the project. |