* The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint.
* The Scrum Team is responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Scrum Team does not rely on any external authority, manager, or leader to assign or monitor their work. The Scrum Team collaborates and coordinates their work as one unit, without any hand-offs or silos. The Scrum Team also inspects and adapts their work based on empirical evidence and feedback.
* The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
* The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
* The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
* The other options are not valid or relevant answers for who should make sure everyone on the Scrum Team does their tasks for the Sprint. They are either nonexistent or irrelevant roles in Scrum. They are:
* The Project Manager: There is no “Project Manager” role in Scrum. Scrum is a framework for developing, delivering, and sustaining complex products, not projects. A project is a temporary endeavor with a fixed scope, time, and cost. A product is a valuable solution that evolves over time to meet customer needs and market conditions. A project manager is a role in traditional project management, a discipline for planning, executing, and controlling projects. A project manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations.
* The Product Owner: The Product Owner is not responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner does not assign or monitor tasks to the Developers. The Product Owner collaborates with them to clarify and refine the Product Backlog items and their acceptance criteria.
* All of the above: This is not a valid answer because it includes two invalid options: The Project Manager and The Product Owner.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
* Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master

Explanation
It is not true that the Product Owner must write all of the Product Backlog items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team. This is because:
* The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders.
* The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.
* The Product Owner is also accountable for managing the Product Backlog items effectively. They must ensure that they are transparent, visible, and understood by everyone who needs to work on them. They must also collaborate with the Developers and stakeholders to refine, order, and prioritize them based on value and impact.
* The Product Owner does not need to write all of the Product Backlog items by themselves or before handing them over to the Scrum Team. They can involve others in creating or contributing to them, such as customers, users, stakeholders, or Developers. They can also add or modify them at any time during the product development process, as long as they are clear and ready for selection in Sprint Planning.
References:
* [Scrum Guide], page 6, section “Product Owner”
* [Scrum Guide], page 11, section “Product Backlog”
* [Scrum Guide], page 10, section “Product Goal”
* [Scrum Guide], page 12, section “Product Backlog Refinement”
* [Scrum Guide], page 14, section “Sprint Planning”

Explanation
The Scrum Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because:
It reflects the current state of the product and the work. The Product Backlog is a dynamic and emergent artifact that represents all the possible features, functions, requirements, enhancements, and fixes that constitute changes to the product. By updating it frequently, the Scrum Team can ensure that the Product Backlog is accurate, complete, and relevant.
It enables the Product Owner to optimize the value of the product and the work of the Scrum Team. The Product Owner is accountable for effective Product Backlog management, which includes ordering, refining, and communicating the Product Backlog items. By updating it frequently, the Product Owner can incorporate new learnings, feedback, opportunities, and changes into the product decisions and priorities.
It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product Backlog is a source of information and transparency for everyone involved in the product development. By updating it frequently, the Scrum Team and the stakeholders can inspect the progress and outcomes of each Sprint, and adapt their plans and actions accordingly.
References:
Scrum Guide 2020, page 10: “The Product Backlog is an emergent, ordered list of what is needed to improve the product.” Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog management, which includes … ensuring that the Product Backlog is transparent, visible and understood.” Scrum Guide 2020, page 11: “The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions.” Scrum Guide 2020, page 11: “Higher ordered Product Backlog items are clearer and more refined than lower ordered ones.” Scrum Guide 2020, page 15: “The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.”

Explanation

Scrum
During the Sprint Retrospective, the Scrum Team discusses how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done123. This includes methods of communication, the way the Scrum Team does Sprint Planning, skills needed to improve the Developers’ ability to deliver, and the Definition of Done123.

The Scrum Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because:
* It reflects the current state of the product and the work. The Product Backlog is a dynamic and emergent artifact that represents all the possible features, functions, requirements, enhancements, and fixes that constitute changes to the product. By updating it frequently, the Scrum Team can ensure that the Product Backlog is accurate, complete, and relevant.
* It enables the Product Owner to optimize the value of the product and the work of the Scrum Team. The Product Owner is accountable for effective Product Backlog management, which includes ordering, refining, and communicating the Product Backlog items. By updating it frequently, the Product Owner can incorporate new learnings, feedback, opportunities, and changes into the product decisions and priorities.
* It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product Backlog is a source of information and transparency for everyone involved in the product development. By updating it frequently, the Scrum Team and the stakeholders can inspect the progress and outcomes of each Sprint, and adapt their plans and actions accordingly.
References:
* Scrum Guide 2020, page 10: “The Product Backlog is an emergent, ordered list of what is needed to improve the product.”
* Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog management, which includes … ensuring that the Product Backlog is transparent, visible and understood.”
* Scrum Guide 2020, page 11: “The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions.”
* Scrum Guide 2020, page 11: “Higher ordered Product Backlog items are clearer and more refined than lower ordered ones.”
* Scrum Guide 2020, page 15: “The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.”

Explanation
* The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
* A Sprint is a timebox of one month or less within which a “Done” product Increment is created. A Sprint consists of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. A Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process.
* During a Sprint, a Product Owner is typically responsible for:
* Collaborating with stakeholders, users, and customers: The Product Owner engages in frequent and regular interactions with the people who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. The Product Owner solicits and incorporates their input, feedback, and insights to understand their needs and expectations, discover new opportunities or ideas, align and collaborate on the product direction and priorities, and validate and deliver value to them.
* Working with the Scrum Team on Product Backlog refinement: The Product Owner works closely with the Developers to clarify, refine, and review the Product Backlog items and their acceptance criteria. The Product Owner provides clear and concise descriptions of what is needed and why it is valuable for each Product Backlog item. The Product Owner also empowers and trusts the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards. The Product Owner also involves key stakeholders in defining and prioritizing the Product Backlog items and their acceptance criteria.
* The other options are not valid or relevant responsibilities of a Product Owner during a Sprint. They are either too administrative, micromanaging, or unrelated to the product value delivery. They are:
* Creating financial reporting upon the spent hours reported by the Developers: This is not a responsibility of a Product Owner during a Sprint. This is an administrative task that does not contribute to the value or quality of the product or service delivered. It may also create unnecessary overhead or bureaucracy for the Developers. The Product Owner should focus on maximizing value rather than tracking hours.
* Updating the work plan for the Developers on a daily basis: This is not a responsibility of a Product Owner during a Sprint. This is a micromanaging task that does not respect the self-organization or cross-functionality of the Developers. The Developers are responsible for planning and executing their own work during a Sprint, based on their empirical experience and collaboration. The Developers also update their progress daily during the Daily Scrum event.
* Nothing: This is not a valid answer for a Product Owner’s responsibility during a Sprint. A Product Owner has many important responsibilities during a Sprint, as mentioned above. A
* Product Owner should be actively involved in collaborating with stakeholders, users, customers, and Developers throughout a Sprint to maximize value delivery.
* Attending every Daily Scrum to answer questions about the Sprint Backlog items: This is not a mandatory responsibility of a Product Owner during a Sprint. The Daily Scrum is an event for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24 hours. The Daily Scrum is not a status meeting or a reporting session for anyone else. The Product Owner may attend the Daily Scrum as an observer or as an invited participant if they have something valuable to contribute or if they need some clarification from the Developers.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum
* Stakeholders: https://www.agilealliance.org/glossary/stakeholders
* Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum

Explanation
The reasons why it is important that there is only one Product Owner per product are:
* It is clear who is accountable for the ultimate value of the product. The Product Owner is accountable
* for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.
* It helps avoid barriers to effective communication and rapid decision-making. The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must also collaborate with the Developers and the stakeholders to refine, order, and prioritize the Product Backlog items based on value and impact.
* The Scrum Team always knows who determines the order of the Product Backlog. The Product Owner has the final authority to decide what items are more important and valuable for the product. They must communicate this order clearly and consistently to the Scrum Team and the stakeholders. They must also respect and support the self-management of the Developers in choosing how best to accomplish their work.
Other options, such as the Scrum Master knowing who acts as their backup while on vacation or it would confuse the stakeholders if they had to work with more than one person, are not valid reasons why it is important that there is only one Product Owner per product. They may reflect a misunderstanding of the roles and accountabilities of the Scrum Team or the stakeholders.
References:
* [Scrum Guide], page 6, section “Product Owner”
* [Scrum Guide], page 11, section “Product Backlog”
* [Scrum Guide], page 12, section “Product Backlog Refinement”
* [Scrum Guide], page 11, section “Product Backlog”
* [Scrum Guide], page 7, section “Developers”

Explanation
* The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
* To ensure that the product delivers value, a Scrum Product Owner might focus on the following aspects:
* How much of the functionality of the product is being used: This is an indicator of how well the product meets or exceeds the needs and expectations of the customers and users. It can also reveal which features or functions are more or less valuable or useful for them. The Product Owner can use various methods or metrics to measure the usage of the product functionality, such as analytics, user behavior, retention, or engagement.
* Direct customer feedback: This is a source of valuable input and insights from the people who use or benefit from the product. It can also help to validate or invalidate assumptions or hypotheses about the product value and quality. The Product Owner can use various methods or channels to collect and incorporate customer feedback, such as surveys, ratings, reviews, interviews, focus groups, or social media.
* How quickly or easily the product can be absorbed and used by its customers: This is a measure of
* how well the product delivers value to customers or users in a timely and convenient manner. It can also affect customer satisfaction and loyalty. The Product Owner can use various methods or metrics to measure the ease of use or adoption of the product, such as time to value, learning curve, usability testing, or net promoter score (NPS).
* The other options are not valid or relevant aspects that a Scrum Product Owner might focus on to ensure that the product delivers value. They are either too narrow, unrealistic, or unrelated to the product value delivery. They are:
* Velocity is increasing over time: This is not a valid aspect that a Scrum Product Owner might focus on to ensure that the product delivers value. Velocity is a measure of how much work a Scrum Team can deliver in a Sprint. It is not a measure of value or quality. It is also not a goal or target for improvement. It is only a planning tool that helps the Scrum Team forecast their future work based on their past performance. Focusing on increasing velocity over time may lead to unrealistic expectations, pressure, or compromise on quality.
* Minimizing changes to project scope: This is not a valid aspect that a Scrum Product Owner might focus on to ensure that the product delivers value. Scrum is an agile framework that embraces change as an opportunity for delivering more value to customers and users. Scrum does not have a fixed project scope, but rather an adaptive Product Backlog that evolves as the product and the market change. The Product Owner should welcome and respond to changes in customer needs and expectations, rather than resist or avoid them.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Value: https://www.scrum.org/resources/blog/value-scrum-value
* Velocity: https://www.agilealliance.org/glossary/velocity

Explanation
The Definition of Done is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done1. A Product Backlog item is considered complete when it meets the Definition of Done, which means that it is usable and potentially releasable, and that it meets the quality standards set by the Scrum Team and the stakeholders2. The other options are not sufficient to determine the completeness of a Product Backlog item, as they may not reflect the actual value and quality of the product.
References:
1: The Scrum Guide, November 2020, p. 13
2: The Scrum Guide, November 2020, p. 6

Explanation
Sprints are fixed-length events of one month or less that serve as a container for the other Scrum events and activities. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. There is no gap or downtime between Sprints. The second Sprint starts right after the first Sprint, regardless of the customer acceptance testing, the architectural changes, or the Product Backlog items.
References:
* The Scrum Guide
* Understanding and Applying the Scrum Framework
* Professional Scrum Product Owner™ I Certification