Intermediate Scrum Practice Test

"The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done."

- from the Scrum Guide

People are often confused about whether the retro is for the developers only. While it might be true that the presence of managers, outsiders, and unfriendly stakeholders can derail this event, the Product Owner and the Scrum Master should definitely participate.

Further reading: Sprint Retrospective

"The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.

During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation."

- from the Scrum Guide

While 'collaborate' is just a word choice that could have been replaced with some synonyms, it is genuinely and generally true that the Sprint Review meeting is the only Scrum event that stakeholders are expected to visit.

Further reading: The Sprint Review

"Each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum. Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless."

- from the Scrum Guide

Implementing Scrum typically requires many process and organisational changes and a cultural shift from the participants. It can be very tempting to cut the corners, cherry-pick some of the easy-to-adopt elements and overrule the rest, however, Scrum is lenient on all of its components.

Further reading: Purpose of the Scrum Guide

"The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work."

- from the Scrum Guide

The latest version of the guide is less detailed on this question, however, it is still clear that only the Developers of the self-managing Scrum Team are in the position to track the progress of a Sprint.

Further reading: Daily Scrum

"If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done." - from the Scrum Guide

In practice, the thumb rule is, the increments should be compatible, inspectable and transparently done to the same standards. This may mean the exact same Definition of Done for all teams or coherent variants taking into account the peculiarities of each team. The wording of the current Guide suggests these teams should use the exact same Definition of Done.

Further reading: The Definition of Done

The Scrum Guide does not prescribe this anymore, however, common sense still suggests that refinement typically impacts Product Backlog items of future Sprints so that they are ready for selection during Sprint Planning. For the current Sprint, it is a bit too late to perform refinement, though better late than never.

"Multiple Scrum Teams working with the same Product Owner must follow the same Definition of Done." - Almost, but it does not depend on the Product Owner but on the Product.

"The Scrum Master serves the Scrum Team by working with other Scrum Masters to define a common Definition of Done." - The Scrum Masters can help their teams in the process of synchronizing their Definition of Done, but the Guide does not prescribe this, and especially not the way that the Scrum Masters define the Definition of Done.

If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.

-- the Scrum Guide

Further reading: The Definition of Done

"A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint. "

- from the Scrum Guide

This is fairly logical since it the who is PO is responsible for the business outcome. Before the first Scrum Guide was published there was no clear consensus whether the developers could also cancel a sprint, e.g. if the PO requests significant changes to the product backlog. Such action would be pretty concerning, however, the PO has the right to negotiate changes to the Product Backlog Items with the Developers.

Further reading: The Sprint

The three correct statements were explicitly stated by the 2017 Scrum Guide. The 2020 version is less elaborate on these questions. However, the truth behind these statements is still supported by the Scrum Guide:

• In the Daily Scrum chapter, it states that this meeting is for the Developers. It also states that the Scrum Master and the Product Owner should participate only if they are 'Developers' themselves (in the sense of working on backlog items).
• In the Scrum Master chapter, it states that Scrum Master ensures all Scrum events take place and are positive, productive, and kept within the timebox.

A time-box is the maximum allocated time for an event.

"The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide."

Further reading: The Scrum Master

"As Scrum’s use spreads, developers, researchers, analysts, scientists, and other specialists do the work. We use the word “developers” in Scrum not to exclude, but to simplify. If you get value from Scrum, consider yourself included." - the Scrum Guide

Whatever "Developers" develop, that is "development". Depending on the context, it may have nothing to do with software development.

Further reading: Purpose of the Scrum Guide

"The Scrum Team may also invite other people to attend Sprint Planning to provide advice."

- from the Scrum Guide

Further reading: Sprint Planning

"The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. [...] If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers."

Thus, this meeting is exclusively for the developers, so much that even the Scrum Master and the Product Owner are not required/expected to participate unless they have developer duties, too. There is no explicit ban for others to occasionally attend but they cannot participate. However, it is still true that outsiders can derail the meeting even with their passive presence.

Further reading: The Daily Scrum

"The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint." - Scrum Guide (2020 version)

"Implement at least one high priority item in the next Sprint" - is what the 2017 guide recommended

Further reading: Sprint Retrospective

"Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint." - from the Scrum Guide

These are the well known

• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective"

"Removing barriers between stakeholders and Scrum Teams."

- from the Scrum Guide

Further reading: The Scrum Master

The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.

Further reading: The Scrum Team

An Increment is a concrete stepping stone toward the Product Goal.

Further reading: The Increment

"Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how." - the Scrum Guide

"The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint." - the Scrum Guide

"Within a Scrum Team, there are no sub-teams or hierarchies." - the Scrum Guide

Further reading: The Scrum Team

The Product Owner is always one person. The Product Owner may receive help from others but still remains responsible for the product.