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.
How To Pass PSM I Exam?Scrum PSM I PDF dumps.High quality PSM I PDF and software. VALID exam to help you pass. |
 |
How To Pass PSM II Exam?Scrum PSM II PDF dumps.High quality PSM II PDF and software. VALID exam to help you pass. |
|
B&C is the answer I chose but I don’t agree with B. Technical debit doesn’t stop an increment being releasable, it’s probably there to get code to a releasable point in the time-box. Technical debit could affect future increments, hence the decision to choose it, but badly worded question IMO.
B & C