A.At the end of the Sprint.

B.When all work in the Sprint Backlog related to the item is finished.

C.When QA reports that the item passes all acceptance criteria.

D.When the item has no work remaining in order to be potentially released.

A.Use coaching techniques; such as open questions and active listening.

B.Ask an external technical specialist to make the decision.

C.Send every team member to the company's HR department to express their concerns.

D.Involve the complete Development Team.

A.It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.

B.When calculated and estimated, the totalamount of technical debt shows exactly how long until the Product Owner can release the Increment.

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.

A.Prioritize the Development Team's work on the Sprint Backlog.

B.Update the Sprint burndown chart.

C.Run the Daily Scrum.

D.Answer questions from the Development Team about items in the current Sprint.

E.Work with the stakeholders.

A.Selecting the Product Owner.

B.Resolving internal team conflicts.

C.Reporting productivity.

D.Organizing the work required to meet the Sprint Goal.