SCRUM Artifacts and Commitments 2

Question 1

What is the commitment associated with the Product Backlog?

Accepted Answer

Product Goal

Answer

Sprint Goal

Answer

Definition of Done

Answer

Increment

Question 2

What is the commitment associated with the Sprint Backlog?

Accepted Answer

Sprint Goal

Answer

Product Goal

Answer

Definition of Done

Answer

Release Plan

Question 3

What is the commitment associated with the Increment?

Accepted Answer

Definition of Done

Answer

Sprint Goal

Answer

Product Goal

Answer

Velocity

Question 4

Why were commitments introduced for each artifact in Scrum?

Accepted Answer

To reinforce empiricism and focus by providing measures of progress

Answer

To add more documentation requirements

Answer

To replace the Scrum events

Answer

To eliminate the need for a Product Owner

Question 5

If a development team produces work that does not meet the Definition of Done, what should happen?

Accepted Answer

The work is not part of the Increment and returns to the Product Backlog

Answer

It is released anyway with a warning

Answer

It is automatically added to the next Sprint Backlog

Answer

The Definition of Done is lowered to match the work

Question 6

Who is responsible for ensuring the Definition of Done is applied when it is an organizational standard?

Accepted Answer

The Scrum Team must follow it as a minimum

Answer

Only the Scrum Master

Answer

Only the Product Owner

Answer

It becomes optional

Question 7

How does the Sprint Goal affect the Developers during the Sprint?

Accepted Answer

It provides flexibility in terms of the exact work needed to achieve it

Answer

It locks the scope so nothing can change

Answer

It replaces the daily collaboration

Answer

It is set by the Scrum Master alone