Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The question is - how will we know that the overall quality of the software in Acquisition & Finance domain is gradually improving as we implement our ideas? This requires metrics that characterize the state of A&F, and of particular importance is the understanding of these metrics in dynamics, over several release cycles. So, what metric can be used?

This Thunderjet - Bugs metrics Jira dashboard provides a lot of interesting statistics in terms of bugs and bugs reported in the Jira tracking system.

...

MetricSense / ExpectationsSourceFrequency of collection / analysis

Number of bugs including their priority

expectation is zero P1Jira dashboardonce per sprint
Number of overall detected bugs by priorities and releasesthe expected trend is to reduce the total number of bugs from release to release while reducing the priority of identified bugsJira dashboardonce per release
Number of bugs escaped into Production

the expected trend is to minimize and even avoid P1/P2 bugs in Production (P3 is acceptable); Production bugs are those which have RRT or Support label

Jira dashboardonce per release
Number of occurrences (similar bugs reported by different customers)
FSE / Rally log, as a part of RCAonce per release

Average time of bug fixing

there does not seem to be any SLA in this area yet, so the expected trend is to decrease this time as a result of improved tools for troubleshooting and analysismanually, by the special scriptonce per release

No performance degradation from release to release

no Baseline metrics in this area; there are only measurements for exporting orders in Edifact format (Morning Glory -> Nolana - it got better)

Action item: contact PTF, write performance tests, organize and load test against a set of scenarios in Orchid to get baseline values

performance testingonce per release

Poppy

Sprint 160

Release

Orchid

Release

Number of overall detected bugs by priorities and releases

Jira ChartsborderfalseshowinforfalseserverSystem Jirajql%22Development%20Team%22%20%3D%20Thunderjet%20and%20Release%20%3D%20%22Orchid%20(R1%202023)%22%20and%20type%20%3D%20BugstatTypeprioritieschartTypepiewidthisAuthenticatedtrueserverId01505d01-b853-3c2e-90f1-ee9b165564fc Jira LegacyserverSystem JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionmaximumIssues20jqlQuery"Development Team" = Thunderjet and Release = "Orchid (R1 2023)" and type = Bug serverId01505d01-b853-3c2e-90f1-ee9b165564fc

Page Tree
rootThunderjet - Quality Metrics