Product Owner

A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for the Product Backlog. However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?

- Stability requirements

- Performance requirements

- Product Functionality

- Documentation

• Yes, they all belong on the Product Backlog. The Product Backlog is supposed to be the "single source of truth" for all the work for the product.

• No. Product Backlog is a tool for the Product Owner. The Product Owner represents the users and stakeholders. Other types of requirements should be managed separately by the Developers. They are not the Product Owner's concern.

The IT manager asks a Scrum Team for a status report describing the progress throughout the Sprint. The Scrum Team asks the Scrum Master for advice. The Scrum Master should:

• Tell the Scrum Team to figure it out themselves.

• Ask the Product Owner to send the manager the report.

• Tell the Developers to fit the report into the Sprint Backlog.

• Create and deliver the report to the manager herself.

• Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.

When there are multiple teams working on one product, each Scrum Team should have a separate Product Owner.

• False

• True

What is the accountability of the Product Owner during Sprint 0?

• Gathering eliciting and analyzing the requirements to build the product backlog.

• Determine the composition of the Scrum Team to meet the release plan.

• There is no Sprint 0

• Create the overall release plan to ensure that organizational goals are met

• Make sure enough Product Backlog items are refined to fill the first 3 Sprints.

Sprint Reviews are an opportunity to collect customer feedback.

• False

• True

Why would you expect a Product Owner to care about the Scrum Team adhering to its Definition of Done? (two answers)

• The Definition of Done can affect the product's total cost of ownership

• To have complete transparency into what has been done at the end of each Sprint

• To be able to punish the team when they do not meet their velocity goal for the Sprint.

• The Product Owner should not care about the Definition of Done, it is the Scrum Team's responsibility.

• To forecast the team's productivity over time.

What is the timebox for the Sprint Review?

• 2 hours for a one-month Sprint.

• 4 hours for a one-month Sprint.

• As long as needed.

• 1 day.

Which of the following is a Developer accountable for? (two answers)

• Organizing the work required to meet the Sprint Goal.

• Creating a plan for the Sprint, the Sprint Backlog.

• Reporting productivity.

• Selecting the Product Owner.

True or False: The Scrum Team is accountable for releasing the most valuable product.

• True

• False

What is the responsibility of the Product Owner in crafting the Sprint Goal?

• The Product Owner defines the scope for a Sprint and therefore also the Sprint Goal.

• The Product Owner has no responsibility in it. This is the Developers responsibility.

• The Product Owner should come to the Sprint Planning with a business objective in mind and work with the Developers to craft the Sprint Goal.

• The Product Owner must work with stakeholders to set each Sprint's Goal.

• The Product Owner should not come to the Sprint Planning without a clearly defined Sprint Goal.