Team SG Cares Bug Log
Jump to navigation
Jump to search
Total = (Lvl 1 Errors) * 1 + (Lvl 2 Errors) * 5 + (Lvl 3 Errors) * 10 + (Lvl 4 Errors) * 15
Contents
Bug Metric
Metric
- Goal: Optimize code quality
- Question: Under what circumstances do we reschedule our project to solve severe bugs?
- Metric: Severity of bugs found in a metric
- Use: To decide when do we reschedule our project to solve severe bugs
Level of Severity | Description | Examples |
---|---|---|
1 | Error has little/no impact to the application, does not need to be fixed unless extra time is available. |
|
2 | Error causes some minor inconvenience to users, but does not affect application functionality. |
|
3 | Error has substantial amount of impact to the application. May cause application to crash. |
|
4 | Error is critical, results in frequent system crashes. |
|
Points Calculation:
Course of Action
Total Points | Course of Action |
---|---|
Points <= 10 | Not important – fix problem(s) during the last iteration, unless there is extra time (and nothing else is more important than this) |
10 < Points <= 15 | Fix the bug(s) during the debugging time until total points is left to 10 and below |
15 < Points | Halt project development immediately to resolve issues until total points is below 10 |