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

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

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

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

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

A.Short enough to keep the business risk acceptable to the Product Owner.

B.Short enough to be able to synchronize the development work with other business events.

C.No more than one calendar month.

D.All of these answers are correct.

A.Whatever the Product Owner defines as quality.

B.All work to create software that is ready to be released to end users.

C.Ready for integration.

D.All work the Development Team is willing to do.

E.No work left from the definition of "Done".

A.All of theabove are allowed depending on the situation.

B.The break between Sprints is time-boxed to 1 week for 30 day Sprints, and usually less for shorter sprints.

C.Enough time for the Development team to finish the testing from the last Sprint.

D.None. A new Sprint starts immediately following the end of the previous Sprint.

E.Enough time for the requirements for the next Sprint to be determined and documented.

A.Product Owner

B.Development Team

C.Customers

D.Users

E.Scrum Master