What conditions are most likely occurring if you feel you need a “Quality Assurance and Release Readiness Sprint”?
(choose the best three answers)
A. The Definition of Done is not being met every Sprint.
B. The Definition of Done is weak or incomplete, allowing technical debt to accumulate.
C. The Developers find it nearly impossible to create a valuable, useful product Increment in a Sprint.
D. You are following Scrum and the concept of a Hardening Sprint.
E. Scrum has been modified in an acceptable manner to introduce “Quality Assurance and Release Readiness Sprints”.

Which four of the following risks to product development are addressed by Scrum?
(choose the best four answers)
A. The complexity and unpredictability of the requirements.
B. The stability and complexity of the technology.
C. The skills and working relationships of the people on the teams.
D. The timescale of the planned work.
E. The clear definitions of stages and gateways in the overall governance model.
F. The definition of incentive and bonus strategies by Human Resources for all team members.

Another team’s Scrum Master seeks your advice. The Daily Scrum always runs longer than 15 minutes. The Developers suggest splitting the Scrum Team into two teams. What is your response?
(choose the best answer)
A. You agree – this is an appropriate solution to the problem.
B. You disagree – you tell the Scrum Master that as Scrum Master they need to manage the timebox better.
C. You disagree – there is not enough information to justify splitting a team into two teams. You ask if there is anything you can do to help your colleague, for example observe one of the Daily Scrums with them.
D. You agree – splitting the team into two is a good strategy to allow the teams to learn how to run Daily Scrums quickly and effectively. Once they have learned to limit the Daily Scrum to 15 minutes, you can combine the teams again.

How should requirements be distributed when multiple Scrum Teams work on the same product?
(choose the best answer)
A. The Scrum Team with the highest velocity pulls items from an overall Product Backlog first.
B. They must be selected from one Product Backlog in such a way that each Scrum Team has an equal volume of requirements per Sprint.
C. The Product Owner decides by providing each team with its own Product Backlog.
D. The Developers pull in work from a shared Product Backlog in agreement with the Product Owner and the other teams.

You are a Scrum Master entering an organization that wants to “evolve” their product development to Scrum. The organization’s teams are organized into component teams. This means that teams address one single application layer only (for example, front end, middle tier, back end, and interfaces).
You introduce the concept of feature teams, where teams have the skills to work on multiple layers throughout a Sprint and deliver working software every Sprint. What are two things you take into consideration when moving away from component teams toward feature teams?
(choose the best two answers)
A. With feature teams, it is easier to calculate and compare the productivity per team. Incentives on productivity are likely to speed up the transition to feature teams, and therefore the adoption of Scrum.
B. Productivity, in terms of lines of code or story points, will probably suffer during the transition, although even then delivery of business value is still likely to increase.
C. You cannot do Scrum without feature teams. Don’t continue adopting Scrum until teams are reorganized in feature teams.
D. Feature teams will require time to become productive as people from the different layers and components become accustomed to working and delivering unified functionality together, as one Scrum Team.

Scrum requires a Definition of Done. Which phrases describe the purpose of the Definition of Done?
(choose the best three answers)
A. It is a checklist to inspect whether the Developers have performed their tasks by the end of a Sprint.
B. It guides the Developers in creating a forecast at the Sprint Planning.
C. During the Sprint it helps the Developers identify the work remaining for an Increment to be ready for release by the end of a Sprint.
D. It serves to track the percent completeness of a Product Backlog item during the Sprint.
E. It creates transparency over the state of the Increment when it is inspected at the Sprint Review.
F. It provides a template for the documentation of the product Increment.