Professional Scrum Master I (PSM I) — Question 29

Select two ways in which technical debt impacts transparency. (Choose two.)

Answer options

• A. When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
• B. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.
• C. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.
• D. It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is technical debt.

Correct answer: B, C

Explanation

Option B is correct because technical debt can create misconceptions about whether an Increment is ready for release, which affects transparency. Option C is also correct as the accumulation of technical debt complicates the system's stability and can lead to unpredictable delays in future work, further obscuring the project's status. Options A and D are incorrect because they do not directly relate to how technical debt impacts transparency.