QuestionQ201

Product

During product development, evolving technology and regulations require the team to reassess the product architecture.

How should this technical debt be recorded?

  • A Include it in the product backlog and use a new indicator to annotate that is technical debt
  • B Include it in the product backlog as a low-priority issue
  • C Since it is not a part of agile methodologies, it should not be tracked
  • D Have team members maintain personal lists of issues and consolidate the lists during review
Explanation

Technical debt should be captured in the product backlog and clearly identified as technical debt. This makes the work visible to stakeholders and allows it to be assessed and prioritized alongside other product work.

Community Discussion

No comments yet. Be the first to start the discussion!