Test Your Agile Knowledge

The product owner is responsible for prioritizing the product backlog. This is because the product owner is the person who understands the customer's needs and requirements the most, and is therefore in the best position to determine which items in the backlog should be worked on first. The product owner works closely with stakeholders and the development team to ensure that the most valuable and important features are prioritized and delivered in a timely manner.

The Product review meeting is not part of Scrum. In Scrum, there are four main meetings: Sprint planning, Daily Scrum, Sprint review, and Sprint retrospective. The Product review meeting is not mentioned as one of the core Scrum meetings. The other three meetings listed are all part of the Scrum framework and play important roles in the iterative development process. The Product review meeting may be a separate meeting outside of Scrum, but it is not a core Scrum meeting.

The correct answer is Product Manager. In Scrum, there are three main roles: Product Owner, Scrum Master, and Team. The Product Owner is responsible for prioritizing and managing the product backlog, while the Scrum Master facilitates the Scrum process and ensures the team follows it. The Team is responsible for delivering the product increment. However, the role of a Product Manager is not part of the Scrum framework. While there may be overlap in responsibilities between a Product Owner and a Product Manager in some organizations, they are distinct roles with different focuses and responsibilities.

A story is not a Scrum artifact. In Scrum, artifacts are tangible and visible items that provide transparency and information to the team. The Product Backlog is a prioritized list of requirements or features, the Sprint Backlog is a subset of the Product Backlog for a specific sprint, and the Burndown Chart tracks the progress of work during a sprint. However, a story is not an artifact but rather a way of describing a user or system requirement in an informal manner.

Velocity is a measure of customer buy-in because it refers to the rate at which a project team delivers value to the customer. It is commonly used in agile methodologies, such as Scrum, to track the amount of work completed in a given time period. The higher the velocity, the more buy-in there is from the customer, as it indicates that the team is successfully meeting their needs and delivering the desired outcomes.