A.Inform the Product Owner's functional manager.

B.Stop the Sprint, send the Product Owner to a course and restart.

C.Bring up the problem in the Sprint Retrospective.

D.Coach the Product Owner in the values of Scrum and incremental delivery.

E.Nominate a proxy Product Owner.

A.The Project Manager.

B.The Development Team.

C.The Product Owner.

D.The Scrum Master.

E.All of the above.

A.The entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting.

B.Just enough to understand design and architectural implications.

C.Just enough tasks for the Scrum Master to be confident in the Development Team's understanding of
the Sprint.

D.Enough so the Development Team can create its best forecast of what is can do, and to start the first
several days of the Sprint.

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.

A.Optimizing the value of the work the Development Team does.

B.Managing the project and ensuring that the work meets the commitments to the stakeholders.

C.Directing the Development Team.

D.Keeping stakeholders at bay.