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

[Scrum Revolution]

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

 

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

Technical debt (also known as tech debt or code debt) describes what results when development teams take actions to expedite the delivery of a piece of functionality or a project which later needs to be refactored. In other words, it’s the result of prioritizing speedy delivery over perfect code. It can lead to false assumptions about the current state of the system or code that has been created and if not picked up it can destabilize the system which causes rework and delays

[Author]

Posts