Why might Developers choose to do pair programming?
(choose the best answer)
A. Information sharing and learning.
B. Improving code quality.
C. Efficiency.
D. It can be a fun way to work.
E. All of the above.

What is the purpose of a Sprint Review?
(choose the best answer)
A. To build team spirit.
B. To take time to judge the validity of the project.
C. To review the Scrum Team’s activities and processes during the Sprint.
D. To inspect the product Increment with stakeholders and collect feedback on next steps.

Which approach is best for Scrum Teams in order to produce valuable Increments?
(choose the best answer)
A. Each Scrum Team is accountable for developing functionality from beginning to end.
B. Each Developer works only on the component where they feel they can contribute.
C. Each Scrum Member works only as an independent layer of the system.
D. Each Scrum Team works on an independent set of components.

Does delivering changes frequently and directly into production help to reduce risk?
(choose the best two answers)
A. Yes, because you get earlier feedback and can learn faster.
B. No, the only way to tackle these risks is by extensive risk management.
C. Yes, because the changes you make are much smaller and it is easier to fix problems.
D. Yes, because frequent releases encourage the Developers to automate the release process.
E. No, because releasing needs extensive testing which cannot be conducted frequently.
F. No, because each release means a risk to break something so releasing more frequently would increase the risk.

Who creates documentation included with an Increment?
(choose the best answer)
A. The Scrum Master.
B. The Developers.
C. The Product Owner.
D. Increments do not need documentation.
E. Technical writers.

Which of the following best describes Continuous Integration?
(choose the best answer)
A. A software development practice that continuously integrates feedback from users into software design.
B. A software development practice where the Developers integrate and verify their work frequently, often multiple times each day, to detect integration errors as quickly as possible.
C. A software development practice used by Integration Teams to create best practice branching and merging strategies.
D. A software development practice where the Developers all work on the same computer to ensure a common code base.