Which three behaviors demonstrate that a Scrum Team is self-managing?
(choose the best three answers)
A. The Scrum Team has all the skills needed to create an Increment.
B. The Developers collaboratively selecting their own work during the Sprint.
C. The Scrum Team members are working within the boundaries of their functional description and nicely handing off work from analyst to developer to tester to integration.
D. Stakeholders are attending the Daily Scrum to check progress and work with the Scrum Master to optimize the functional scope for the Sprint.
E. The Developers create their own Sprint Backlog, reflecting all work that is part of the Definition of Done.
F. The Scrum Master is no longer needed.

You are asked to refactor part of the codebase for Application X. When you are done, all unit tests pass with 50% code coverage. What can you infer from this?
(choose the best answer)
A. Less than 50% of Application X functions correctly.
B. At least 50% of Application X functions correctly.
C. You did not break any existing unit tests.
D. There are no bugs present in Application X.

Which outcome is expected as a Scrum Team matures?
(choose the best answer)
A. There is no need for a timeboxed Sprint.
B. A Scrum Master is no longer needed since they are a mature team now.
C. They will improve their Definition of Done to include more stringent criteria.
D. The Sprint Retrospectives will grow to be longer than 4 hours.
E. Sprint Reviews will no longer be needed.

Product Backlog items are refined by:
(choose the best answer)
A. The Product Owner.
B. The Business Analyst and the Product Owner.
C. The Developers.
D. The Scrum Team.

What are three advantages of Continuous Integration?
(choose the best three answers)
A. Broken builds are detected quickly.
B. Readability of code is improved.
C. The software is generally kept in a buildable state.
D. Know immediately how a check-in affected the build.

Which are attributes of a good bug report?
(choose all that apply)
A. Expected results and observed results.
B. Clear title and proper grammar in report.
C. Build/version where bug was found.
D. One bug per report.
E. Provides simple and repeatable reproduction steps.
F. Screenshots or other pictures of bug in action when user interfaces are involved.