A.Update the Sprint burndown chart.

B.Prioritize the Development Team's work on the Sprint Backlog.

C.Answer questions from the Development Team about items in the current Sprint.

D.Run the Daily Scrum.

E.Work with the stakeholders.

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.Put them on a separate list on the Scrum board, available for all to see.

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

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

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

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

C.Add the item to the next Sprint.

D.Add the itemto the current Sprint without any adjustments.

A.To know what the team will deliver over the next three Sprints.

B.To have complete transparency into what has been done at the end of each Sprint.

C.To be able to reprimand the team when they don't meet their velocity goal for the Sprint.

D.To predict the team's productivity over time.

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.All of these answers are correct.

D.No more than one calendar month.