Product Backlog

When is a Product Backlog considered "complete"?

• When the Product Owner says it is.

• When the Stakeholders say it is.

• When the team says it is.

• The Product Backlog is never "complete".

Who is ultimately responsible for managing the Product Backlog content, ordering, and availability?

• The Team

• The Scrum Master

• Stakeholders and the Product Owner

• The Product Owner

Which of the following is not typically included as an attribute in a Product Backlog Item?

• Description

• Estimate

• Deadline

• Acceptance Criteria

Question 5:

When is it acceptable to update a Product Backlog Item? Pick the best answer.

• During Sprint Planning

• During Daily Stand-up

• During Backlog Grooming

• At any time.

What % of a Development Teams capacity should be dedicated to Product Backlog Refinement?

• At least 10%

• Not more than 10%

• At least 15%

• Not more than 15%

• As much time as is needed

True or False. If multiple Scrum teams work on the same product, they should always use a single shared Product Backlog.

• True

• False

The Product Backlog is ordered based on ..........

​

Effort

• Effort

• Feasibility

• Priority as determined by the Product Owner

• Deadlines

In Scrum, each artifact contains a commitment. What are the 3 commitments?

• The Product Goal, The Definition of Ready & The Definition of Done

• The Definition of Done, The Time-box & The Product Goal

• The Product Goal, The Definition of Done & The Sprint Goal

• The Increment, The Product Goal & The Time-box

The Product Backlog is an ordered list of ............. considered to be necessary for the product.

• Features

• Fixes

• Technical Enhancements

• All answers are correct