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

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

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

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

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

A.Development Team

B.Scrum Master

C.Customers

D.Product Owner

E.Users

A.9.

B.3 to 9.

C.7 plus or minus 3.

D.At least 7.

A.Run the integration and regression tests before the end of the Sprint, and capture the open work for the
Sprint Backlog of the next Sprint.

B.Run the integration and regression tests before the end of the Sprint, and capture the open work for the
Sprint Backlog of the next Sprint.

C.Put them on a separate list on the Scrum board, available for all to see.

D.Add them to the Product Backlog and keep the Product Owner posted on the expected effort.

E.Add them to the definition of "Done" so the work is taken care of every Sprint.

A.Product Backlog items must be estimated in story points.

B.Estimates are made by the Development Team.

C.Scrum forbids estimating.

D.Estimates are made by the Product Owner, but are best checked with the Development Team.

E.Estimates must be in relative units.