Delivery Quality (QC Scorecard)

Development velocity and SonarQube tell us about throughput and code. This page is about product and delivery quality - how effectively we catch defects and ship the right thing. The Quality Engineer (QC) team measures it with a single weighted scorecard that rolls up to one overall QC score.

The scorecard at a glance

Three weighted categories sum to 100%. Each contains measurable sub-metrics with their own weights.

pie showData
    title QC Scorecard - category weights
    "Defect Detection Effectiveness" : 45
    "Test Design & Sprint Monitoring" : 35
    "Ticket Rejection Rate" : 20

Full breakdown

Category (weight)	Metric (weight)	What it measures
Defect Detection Effectiveness (45%)	Defect Detection Rate (25%)	Bugs QC catches vs. bugs the BA finds - the team’s raw detection ability.
	Bug Containment Rate (20%)	% of bugs kept from leaking to UAT / Production.
Test Design & Sprint Monitoring (35%)	Bug-to-Test-Case Traceability Rate (20%)	% of bugs caught by pre-designed test cases - how systematic (vs. ad-hoc) the testing is.
	Sprint Delivery Monitoring Rate (15%)	% of tickets delivered on time, excluding external blocks - QC ownership of sprint commitments.
Ticket Rejection Rate (20%)	BA Acceptance Rate (12%)	% of tickets accepted by the BA without requirement rejection - requirement understanding.
	First Pass Rate (8%)	% of tickets passing review on first submission - overall output quality.

How the categories add up

flowchart LR
    DDR[Defect Detection Rate<br/>25%] --> DDE[Defect Detection<br/>Effectiveness · 45%]
    BCR[Bug Containment Rate<br/>20%] --> DDE
    BTT[Bug-to-Test-Case<br/>Traceability · 20%] --> TDS[Test Design &<br/>Sprint Monitoring · 35%]
    SDM[Sprint Delivery<br/>Monitoring · 15%] --> TDS
    BAR[BA Acceptance Rate<br/>12%] --> TRR[Ticket Rejection<br/>Rate · 20%]
    FPR[First Pass Rate<br/>8%] --> TRR
    DDE --> SCORE((Overall QC Score<br/>100%))
    TDS --> SCORE
    TRR --> SCORE

The score formula

The overall QC score is the weighted sum of each metric’s value:

QC Score = Σ ( metric value % × metric weight )

For example, with the weights above, a sprint where every sub-metric sits at 90% yields an overall score of 90%. The weights mean improvements in defect detection move the score most, reflecting that catching defects early is the team’s highest-value contribution.

What each metric drives us to improve

Metric	Improve it by…
Defect Detection Rate	Stronger test design, exploratory testing, AI-generated edge cases.
Bug Containment Rate	Catching defects earlier in the sprint, not at UAT; tighter DoD.
Bug-to-Test-Case Traceability	Designing test cases from acceptance criteria up front, not reactively.
Sprint Delivery Monitoring	Realistic commitment, early blocker escalation, owning the sprint board.
BA Acceptance Rate	Better requirement comprehension; clarifying with the BA before building.
First Pass Rate	Higher code & test quality before submission (links to Code Quality).

Monitoring cadence

Sub-metrics are captured per sprint from the issue tracker and test management tool.
The rolled-up score is reviewed at the Retrospective, where AI clusters the contributing data into themes.
We track the trend per metric, not just the headline score - a stable overall score can hide a declining sub-metric.