SCRUM - Scrum Framework Artifacts and Commitments Questions and Answers

Question 1

If an organization does not have a formal standard for a Definition of Done, who is accountable for creating one appropriate for the product?

Accepted Answer

The Scrum Team

Answer

According to the 2020 Scrum Guide, if the Definition of Done is not an organizational standard, the Scrum Team must create one that is appropriate for the product. This is a collaborative effort involving the Product Owner, Scrum Master, and Developers to ensure a shared understanding of what it means for work to be complete.

Question 2

A Developer completes a Product Backlog Item on the third day of a two-week Sprint. The work meets all criteria in the Definition of Done. What is the state of this completed item?

Accepted Answer

A usable Increment

Answer

The Scrum Guide states, "The moment a Product Backlog item meets the Definition of Done, an Increment is born." An Increment must be in a usable state, and multiple Increments can be created within a single Sprint. It does not need to wait until the end of the Sprint or the Sprint Review to be considered an Increment.

Question 3

Which of the following best describes the Product Goal's relationship to the other Scrum artifacts and commitments?

Accepted Answer

It is a long-term objective that gives context to the Product Backlog and guides the creation of Sprint Goals.

Answer

The Product Goal is the long-term objective for the Scrum Team and resides in the Product Backlog, providing context and a target to plan against. Each Sprint Goal is a stepping stone toward the Product Goal. The Product Goal guides the ordering of the Product Backlog and the purpose of each Sprint, it is not simply a sum of Sprint Goals or a fixed contract.

Question 4

During a Sprint, the Developers realize their initial plan for delivering the selected Product Backlog Items is flawed and will not achieve the Sprint Goal. What is the MOST appropriate course of action?

Accepted Answer

Adapt the Sprint Backlog by creating a new plan to meet the unchanged Sprint Goal.

Answer

The Sprint Backlog is a plan by and for the Developers and is expected to change as more is learned. The Sprint Goal, however, is a fixed commitment for the Sprint. The Developers should adapt their plan (the 'how' and the 'what' in the Sprint Backlog) throughout the Sprint to ensure they achieve the Sprint Goal (the 'why'). They may negotiate the scope of the Product Backlog Items with the Product Owner if necessary, as long as the Sprint Goal is not endangered.

Question 5

What is the primary purpose of having commitments for each of the three Scrum artifacts?

Accepted Answer

To enhance transparency and focus, enabling empiricism.

Answer

The Scrum Guide explicitly states that each artifact's commitment exists to ensure it provides information that enhances transparency and focus, against which progress can be measured. This transparency is fundamental to the empirical pillars of inspection and adaptation.

SCRUM Practice Test

SCRUM Practice Test

SCRUM - Scrum Framework Artifacts and Commitments Questions and Answers