A.When the Product Owner is ready.

B.Immediately after the conclusion of the previous Sprint.

C.The Monday following the Sprint Review.

D.Immediately following the next Sprint Planning.

A.Sprint Retrospective.

B.Release Retrospective.

C.Sprint Testing.

D.Sprint Planning.

E.Release Planning.

F.Sprint 0.

G.Daily Scrum.

A.When the Product Owner is absent too often.

B.When a technical dependency cannot be resolved.

C.When functional expectations are not well understood.

D.It can't. Only Product Owners can cancel Sprints.

E.When the selected Product Backlog items for the Sprint become unachievable.

A.Directing the Development Team.

B.Keeping stakeholders at bay.

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

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

A.A new user interface design for functionality delivered in previous iterations.

B.Additional features in a usable state that complement those delivered in previous iterations.

C.An automated test suite to verify functionality delivered in previous iterations.

D.A decomposition of all Product Backlog items into tasks for future Sprint Backlog lists.

E.UML diagrams that describe how to deliver functionality in future iterations.