A.A cookbook that defines best practices for software development.

B.A framework within which complex products in complex environments are developed.

C.A defined and predictive process that confirms to the principles of Scientific Management.

D.A complete methodology that defines how to develop software.

A.Suggest the Product Owner extend the Sprint, so he can have more time to order the Product Backlog.

B.Suggest that the Development Team does the ordering to be sure that it is a feasible ordering of work.

C.Present the Product Owner with an ordered Product Backlog to use.

D.Encourage the Product Owner to work with the Development Team to see which items technically are fastest to implement.

E.Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.

A.Inform the Product Owner so he/she can work with the CEO.

B.Add the item to the current Sprint without any adjustments.

C.Add the item to the current Sprint and drop an item of equal size.

D.Add the item to the next Sprint.

A.Just enough to understand design and architectural implications.

B.Just enough tasks for the Scrum Master to be confident in the Development Team's understanding of the Sprint.

C.The entire Sprint Backlog must be identified and estimated by the end of the SprintPlanning meeting.

D.Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.

A.Reduce the definition of "Done" and get all of the Product Backlog items "Done" by the new definition.

B.Inform the Product Owner at the Sprint Review, but prior to the demonstration.

C.Find another Scrum Team to give the excess work to.

D.As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.