A.Opportunities to insect and adapt the Sprint Backlog are lost.

B.Impediments are raised and resolved more slowly.

C.The Product Owner cannot accurately report progress to the stakeholders.

D.Too much work is spent updating the Scrum board before the meeting.

E.The Scrum Master loses the ability to update the Gantt chart properly.

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

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

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

D.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.

E.The Scrum Master is no longer needed.

F.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.

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

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

A.All of the above.

B.Commitment.

C.Openness

D.Focus

E.Respect

F.Courage

A.Do all of the development work, except for specialized testing that requires additional tools and environments.

B.Turn Product Backlog items into an Increment of potentially releasable product functionality.

C.Complete the project within the date and cost as calculated by the Product Owner.

A.The evolution of the cost spent on the project.

B.When all work will be completed to the Scrum Team can be released for other work.

C.When the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.

D.When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added.