To what extent does technical debt limit the value a Product Owner can get from a product? (Choose the best two answers)

Question

Options

• ATechnical debt is not a Product Owner concern, technical debt is only an issue for the Developers.
• BTechnical debt causes a greater percentage of the product's budget to be spent on maintenance of
• CTechnical debt does not influence the delivery of value.
• DThe velocity at which new functionality can be created is reduced when you have technical debt.

• A
  23% (5)
• B
  68% (15)
• C
  9% (2)

Explanation

Technical debt directly limits the Product Owner's ability to deliver value in two key ways. B is correct because maintenance of existing code consumes budget that could otherwise fund new features - the more debt accumulated, the higher the "tax" on every sprint. D is correct because technical shortcuts taken earlier make the codebase harder to modify, slowing down the delivery of new functionality and reducing throughput over time.

A is wrong because technical debt is absolutely a Product Owner concern - it affects the team's capacity, the cost of delivery, and ultimately what can be built within budget and timelines. C is wrong for the same reason: technical debt directly influences value delivery by consuming resources and slowing development velocity.

Memory tip: Think of technical debt like a credit card balance - the Product Owner feels the impact through higher "interest payments" (maintenance costs = B) and less spending power for new things (slower feature delivery = D).

No community discussion yet for this question.