HeaderSIS.jpg

IS480 Team wiki: 2017T2 Appsolute Metrics

From IS480
Jump to navigation Jump to search
Appsolute.jpg

Appsolute Home.png   HOME

Appsolute AboutUs.png   ABOUT US

Appsolute ProjectOverview.png   PROJECT OVERVIEW

Appsolute management.png   PROJECT MANAGEMENT

Appsolute documentation.png   DOCUMENTATION

PROJECT SCHEDULE METRICS RISK MITIGATION CHANGE MANAGEMENT

PROJECT MANAGEMENT METRICS


Appsolute sprintVeloMidTerm.jpg
Sprint 9
Sprint 10
Sprint 11
Sprint 12
Sprint 13
Sprint 14


Appsolute BurnDown10.jpg
Sprint 3
Sprint 4
Sprint 5
Sprint 6
Sprint 7
Sprint 8
Sprint 9
Sprint 10
Sprint 11
Sprint 12
Sprint 13


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


Appsolute BugCount.jpg


Appsolute BugScore.jpg