What are three ways Scrum promotes self-organization? (Choose three.)

1. A. By not allowing documentation.
2. B. By the Development Team deciding what work to do in a Sprint.
3. C. By preventing stakeholders from entering the development room.
4. D. By removing titles for Development Team members.
5. E. By being a lightweight framework.

Correct Answer: BDE
According to the Scrum Guide1, Scrum promotes self-organization by giving autonomy and empowerment to the Developers who decide how to do their work within a Sprint. The Developers have no titles other than Developer, regardless of their specialization or skills. Scrum is a lightweight framework that minimizes prescription and maximizes flexibility and adaptability.
References: Scrum Guide

True or False: The Product Owner makes sure the Developers select enough from the Product Backlog tor a Sprint to satisfy the stakeholders.

1. A. True
2. B. False

Correct Answer: B
According to the Scrum Guide, the Product Owner does not make sure that the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are responsible for selecting how much work they can do in a Sprint, based on their capacity and past performance. The Product Owner may influence them by ordering and clarifying the Product Backlog items, but does not control their selection.

Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces). What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)

1. A. You cannot do Scrum without feature teams.
2. B. Productivity may suffer when making this kind of move.
3. C. Getting support from the business side first helps.
4. D. Feature teams have less communication overhead.
5. E. With feature teams, it is easier to calculate the productivity per team.

Correct Answer: BCD
The correct answers are B, C, and D, because moving away from component teams toward feature teams may involve some challenges and trade-offs. Productivity may suffer when making this kind of move, as teams need to learn new skills, coordinate with other teams, and deal with legacy code. Getting support from the business side first helps, as they can provide the vision, value, and feedback for the features. Feature teams have less communication overhead, as they can deliver end-to-end functionality without depending on other teams.
References: [Suggested Reading for Professional Scrum Master™ I]

How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?

1. A. The Scrum Team with the highest velocity pulls Product Backlog items first.
2. B. The Development Teams pull in work in agreement with the Product Owner.
3. C. The Product Owner should provide each team with its own Product Backlog.
4. D. Each Scrum Team takes an equal numbers of items.
5. E. The Product Owner decides.

Correct Answer: B
The correct answer is B, because when multiple Scrum Teams work from the same Product Backlog, they should pull in work in agreement with the Product Owner. The Scrum Guide states that “multiple Scrum Teams often work together on the same product. One product goal unites them. Therefore, they must mutually define and comply with a definition of ‘Done’ that applies to their combined work product.” Therefore, they should collaborate and coordinate with each other and with the Product Owner to select Product Backlog items that align with their shared product goal.

Who should make sure everyone on the Development Team does their tasks for the Sprint?

1. A. The Project Manager.
2. B. The Product Owner.
3. C. The Scrum Master.
4. D. The Development Team.
5. E. All of the above.

Correct Answer: D
According to the Scrum Guide1, the Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. No one tells them how to do their work. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The other roles are not responsible for making sure everyone on the Development Team does their tasks for the Sprint.
References: Scrum Guide