8.4Managing Test Debt Across Sprints

Reserve Capacity

Reserve 10-20% of sprint capacity for test infrastructure work. This is not optional -- it is an investment that pays dividends in velocity.

Sprint 24 Capacity: 40 story points
  Feature work: 32 points (80%)
  Test debt reduction: 8 points (20%)
    - Fix 4 flaky tests (3 points)
    - Automate 5 manual test cases (3 points)
    - Refactor checkout page objects (2 points)

Track Test Debt in the Backlog

Test debt items should live in the backlog alongside feature work, with the same visibility and prioritization.

Backlog items:
  [Feature] SHOP-900: New checkout flow (8 points)
  [Feature] SHOP-901: Search improvements (5 points)
  [Debt]    QA-050: Fix 6 flaky payment tests (3 points)
  [Debt]    QA-051: Reduce browser test suite from 25min to 15min (5 points)
  [Debt]    QA-052: Migrate hardcoded URLs to environment variables (2 points)
  [Debt]    QA-053: Automate manual login test scenarios (3 points)

Make Debt Visible

Track and report test debt metrics alongside feature metrics:

Sprint 24 Quality Health Report
──────────────────────────────
Flaky Tests:      12 → 8 (fixed 4 this sprint)
Pipeline Time:    22 min → 18 min (added test sharding)
Automation Ratio: 78% → 82% (automated 5 manual test cases)
Manual Test Time: 6 hours → 4.5 hours (1.5 hours saved per regression)

Debt Items Resolved:  4
Debt Items Added:     2 (new feature created 2 new debt items)
Net Debt Change:      -2 (reducing!)