Interactive Lab

Case: Quality Debt vs. Feature Velocity Trade-offs

Interactive Lab

Exercise 1 of 2 | Points: 0 / 60

Back to Case

Technical Debt Quantification

intermediate

Quantify the real cost of technical debt on development velocity.

25
points

Instructions

Using the provided codebase metrics, calculate the actual cost
of technical debt in terms of developer productivity.

Steps:

  1. Analyze bug rate per feature delivery
  2. Calculate time spent on maintenance vs features
  3. Measure velocity degradation over past 6 months
  4. Project future velocity with and without debt reduction
  5. Express debt cost in developer-hours per sprint

Submit with:

  • debt_cost_per_sprint: hours lost per 2-week sprint
  • velocity_degradation_rate: monthly percentage
  • break_even_point: sprints until debt payoff recovers investment
  • projection: 6-month velocity forecast with/without action
  • confidence: 0.0 to 1.0

Initial Data

{
  "quality_score": 68,
  "bug_rates": {
    "avg_bug_fix_hours": 6,
    "bugs_per_sprint": 8,
    "features_with_bugs": 0.35
  },
  "maintenance_ratio": 0.4,
  "monthly_velocity_history": [
    {
      "month": "Sep",
      "story_points": 45
    },
    {
      "month": "Oct",
      "story_points": 42
    },
    {
      "month": "Nov",
      "story_points": 38
    },
    {
      "month": "Dec",
      "story_points": 35
    },
    {
      "month": "Jan",
      "story_points": 32
    },
    {
      "month": "Feb",
      "story_points": 29
    }
  ],
  "sprint_length_days": 10,
  "target_quality": 75,
  "team_size": 8
}

Your Submission

Exercises

Available Tools

Code Metrics
Velocity Tracker

Score

0
of 60 points