A.The Scrum process, and how it was used during the Sprint.

B.Sprint results.

C.Coding and engineering practices.

D.All of the above.

A.Each Development Team uses its own but must make their definition clear to all other teams so the differences are known.

B.All Development Teams must have a definition of "Done" that makes their combined work potentially releasable.

C.It depends.

D.Each Development Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.

A.The value of work currently represented in the Product Backlog.

B.Team relations.

C.Definition of "Done".

D.How the team does its work.

E.Arranging the Sprint Backlog for the next Sprint.

A.The Sprint is extended and future Sprints use this new duration.

B.The Sprint length holds and the Development Team continuously learns what is actually possible to do within a Sprint of this length.

C.The Sprint is extended temporarily. Lessons are taken to ensure it doesn't happen again.

A.To make sure every team member answers the three questions.

B.To gather status and progress information to report to management.

C.To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.

D.He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.