IS480 Team wiki: 2017T2 Appsolute Metrics
Jump to navigation
Jump to search
PROJECT SCHEDULE | METRICS | RISK MITIGATION | CHANGE MANAGEMENT |
PROJECT MANAGEMENT METRICS
BUG METRICS
FORMULA |
---|
Total score = Num of bugs (Low) * 1 + Num of bugs (High) * 5 + Num of bugs (Critical) * 10 |
IMPACT SCORE | |
---|---|
SEVERITY | DESCRIPTION |
LOW IMPACT ( 1 Point ) | Minor issues in the application as a result of oversight or carelessness. Progress of development is not affected and bugs can be easily resolved |
HIGH IMPACT ( 5 Points ) | Issues in the application arise from logic errors. Application can be compiled and run but some functionalities are not working properly. Team's progress is slightly hindered. |
CRITICAL IMPACT ( 10 Points ) | Issues in the application is severe and crashes the system. Development is unable to continue without fixing the issue immediately. |
MITIGATION PLAN | |
---|---|
BUG SCORE | ACTION |
SCORE <= 20 | Good progress - Team can proceed with the planned schedule. Track any bugs and fix them during the planned debugging session only |
21 < SCORE <= 40 | Slight Delay in the development of application. Scrum master is to review the planned schedule and reallocate the tasks where appropriate |
SCORE > 40 | Critical delay in development of application. Team has to come together for discussion. The remaining functionalities to be completed according to the amount of time left for the sprint |
BUG METRICS CHARTS
|