A.Begin facilitating productive and useful Sprint Retrospectives.

B.Consult with the Product Owner to see how he/she feels about the situation.

C.Comply with the decision of the self-organizing team.

D.Call a meeting between the Development Team and senior management.

A.The Scrum Master teaches the Development Team to keep the Scrum meetings to their time-box.

B.The Scrum Master assigns tasks to Development Team members when they need work.

C.The Scrum Master helps those outside the team interact with the Scrum Team.

D.At the Sprint Review, the Scrum Master identifies what has been "done" and what has not been "done".

E.The Scrum Master is responsible for updating the Sprint Burndown.

A.Ensuring that the most valuable functionality is produced first, at all times.

B.Creating detailed functional test cases.

C.Providing the Development Team with detailed specifications.

D.Describing features as Use Cases.

E.Interacting with stakeholders.

A.Earned Value.

B.Focus.

C.Respect.

D.Courage.

E.Economic Value Added.

A.Stakeholders walking in at the Daily Scrum to check progress and work with the Scrum Master to optimize the functional scope for the Sprint.

B.The Product Owner doesn't need to be at Sprint Retrospectives.

C.Development Team members collaboratively selecting their own work during the Sprint.

D.The Development Team members are working within the boundaries of their functional description and nicely handing off work from analyst to developer to tester to integration.

E.The Scrum Master is no longer needed.

F.The Development Team has all the skills needed to create a releasable Increment.

G.The Development Team creating their own sprint backlog, reflecting all work that is part of the definition of "Done".

H.The Development Team inviting external people to the Sprint Planning to ask them how to turn a Product Backlog item into an Increment via a complete and detailed Sprint Backlog.