A. Product Owner
B. Project Manager
C. Scrum Master
D. Developers
A. True
B. False
B. Scrum Master
C. Senior Executives
A. A risk of not creating a potentially shippable product occurs
B. The burndown chart is updated
C. Additional testers are added in the next Sprint
D. The User Story is moved to the next Sprint
A. Increase transparency.
B. Guide the Developers on how many Product Backlog items to select for the Sprint.
C. Describe the purpose, objective, and time-box of each Scrum event.
D. Create a shared understanding of when work is complete.
E. Describe the work that must be done before the Sprint is allowed to end.
A. The business analyst who represents the Product Owner in the Developers.
B. The Product Owner.
C. The Scrum Master, or the Scrum Master may have the Developers do it.
D. The Scrum Master.
A. All development work and at least some testing.
B. As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.
C. A proportional amount of time on analysis, design, programming, testing, and documentation.
D. As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the Definition of "Done".
A. A business analyst represents the Product Owner to make decisions on his behalf during the Sprint. This way the Product Owner can accept the work at the Sprint Review without further involvement.
B. By making sure a Sprint does not stop until all testing is done, and the work is verified by the Product Owner.
C. Through frequent delivery of Increments of the product into the market.
D. At the end of each Sprint, a detailed report with all test cases and test results is available.
E. Through the assurance that a Developers finishes all work on the Sprint Backlog.
A. Prevent interruptions
B. Ensure the three questions are answered
C. Manage the time-box
D. Document impediments
