What should the practitioner do?

Technical debtrefers to the accumulated cost of suboptimal design or code, often due to shortcuts or lack of refactoring. ThePMI Agile Practice Guide (Section 5.5 Quality and Technical Debt)recommends treating technical debt as animpedimentthat should be logged, tracked, and discussed openly so it can be prioritized and addressed.

Mike Griffiths in hisPMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution)advises teams to be transparent about technical debt and elevate its visibility so that product owners and stakeholders can make informed decisions.

Option Cis correct: logging technical debt as animpedimentbrings visibility and ensures discussion.

Option Amay indicate a problem, but it’s indirect.

Option Bdistorts estimation metrics and is not advised.

Option Dcould help but does not communicate impact explicitly.