A. The order of items in the Product Backlog.

B. How the team collaborates.

C. Identifying high priority process improvements for the next Sprint.

D. Documenting acceptance criteria for items in the next Sprint.

A. The opportunity to inspect and adapt is lost. Opaqueness has replaced transparency. Predictability has dropped below zero. The produced software is not usable. As the rules of Scrum have not been respected, it is the Scrum Master's duty to assess whether repair is possible, or a restart with a more reliable team. If not, the Scrum Master should cancel the project.

B. Add enough people to the Development Team for the deadline to be made.

C. The Development Team should remind Marian to find funding for enough Release Sprints in which the remaining work can be done.

D. The Development Team makes sure that all of the selected scope per Sprint is as "Done" as possible.
The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn't mess up the Product Backlog.

A. 10 or fewer.

B. 9

C. At least 7.

D. 7 plus or minus 3.

A. It consists of the Scrum Master asking the Team members the three questions.

B. It is fifteen minutes or less in duration.

C. Its location and time remain constant.

D. It is free from and designed to promote conversation.

E. It is facilitated by the team lead.

F. It is held first thing in the morning.

A. At the Sprint planning meeting.

B. During the Daily Scrum.

C. Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one
may be done by an individual Development Team member.

D. Whenever a team member can accommodate more work.