https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf

Scrum is a framework for developing, delivering, and sustaining complex products. Scrum has three roles: the Product Owner, the Scrum Master, and the Developers. The Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment in each Sprint. The Developers are not limited by titles such as programmer, designer, tester, architect, engineer, etc. The Developers are responsible for all aspects of quality, including finding and fixing bugs, tracking quality metrics, and verifying the work of other Developers. Therefore, Scrum has no “tester” role, and the Developers are responsible for quality.

The correct answer is B, because the time-box for the Sprint Planning meeting is 8 hours for a monthly Sprint. The Scrum Guide states that “Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.”

According to the Scrum Guide 1 , each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. The time-box for the Sprint Review is four hours for a one-month Sprint.

The correct answers are B, E, and F, because these activities would probably help the team in starting up. Having the Scrum Team members introduce themselves and give a brief background of their skills and work history helps build trust and rapport among them. Ensuring the team understands they need a definition of “Done” helps create transparency and alignment on the quality standards for the product. Asking the Product Owner to discuss the product or project, its history, goals, and context, as well as answer questions helps clarify the vision and value of the product.

The correct answers are B and C. According to the Scrum Guide, the Developers are accountable for creating a plan for the Sprint, which is the Sprint Backlog. That makes Option C correct. They are also accountable for organizing the work required to meet the Sprint Goal, which makes Option B correct. These are core elements of self-management in Scrum. Developers decide how to turn selected Product Backlog items into a valuable, usable Increment and how to adapt their plan throughout the Sprint.

Option A is incorrect because Scrum does not define “reporting productivity” as a Developer accountability. Scrum focuses on outcomes, transparency, and progress toward the Sprint Goal rather than traditional productivity reporting. Option D is incorrect because selecting the Product Owner is not a Developer accountability. Role assignments are determined by the organization, not by the Developers.

These accountabilities matter because Scrum relies on Developers to manage their own work rather than wait for direction from others. By creating and adapting the Sprint Backlog and organizing work toward the Sprint Goal, the Developers enable collaboration, flexibility, and accountability for producing a Done Increment each Sprint.

Scrum promotes self-management by empowering the Scrum Team to take ownership of their work and processes. The best three answers are:

A. By having the Scrum Master protect the Scrum Team: The Scrum Master plays a key role in shielding the team from external distractions and impediments, allowing the team to focus on self-management and delivering value.

B. By the Scrum Team deciding what work to do in a Sprint: During Sprint Planning, the Scrum Team collaboratively selects and commits to the work they can accomplish within the Sprint, fostering self-organization and decision-making.

C. By being a lightweight framework: Scrum ' s simplicity and minimal structure provide the team with the flexibility to adapt and manage their work, encouraging self-management without imposing rigid controls.

The correct answer is A because the Sprint Backlog is created during Sprint Planning. The Sprint Backlog is composed of the Sprint Goal, the Product Backlog items selected for the Sprint, and a plan for delivering them. During Sprint Planning, the Scrum Team collaborates to decide why the Sprint is valuable, what can be done during the Sprint, and how the chosen work will be accomplished. This is when the Sprint Backlog comes into existence.

Option B is incorrect because although Product Backlog refinement may prepare items before Sprint Planning, the Sprint Backlog itself is not created until the Sprint Planning event. Option C is incorrect because refinement supports readiness and clarity of Product Backlog items, but it does not establish the Sprint Backlog. Option D is incorrect because the Sprint Retrospective is focused on improvement of the team’s effectiveness and ways of working, not on creating the Sprint Backlog for the next Sprint.

This distinction matters in Scrum because Sprint Planning formally begins the Sprint by creating a clear commitment around the Sprint Goal and the work needed to produce a useful Increment.

The correct answers are B and E, because these statements are true about the length of the Sprint. It is best to have Sprints of consistent length throughout a development effort, as this helps establish a reliable rhythm and cadence for the Scrum Team and the stakeholders. All Sprints must be one month or less, as this ensures that the Scrum Team can inspect and adapt frequently and deliver value incrementally.

According to the Scrum Guide 1 , a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.

The correct answer is A, because the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner is to monitor communications between them and facilitate direct collaboration. The Scrum Guide states that “the Scrum Master serves the Product Owner in several ways, including … facilitating Scrum events as requested or needed.” Therefore, the Scrum Master should help the Development Team and the Product Owner interact regularly and productively during the Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective events.