Correct Answer: D) Never. The entire Scrum Team is accountable for creating

According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The Scrum Team is responsible for all product-related activities, including delivering a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing the value of the product and the work of the Developers. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team's progress.

Therefore, the Developers are not individually accountable for the value of a Product Backlog item selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a Product Backlog item is determined by the Product Owner, who orders the Product Backlog items based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to understand the value and requirements of each Product Backlog item and deliver a potentially releasable product increment that meets the Definition of Done and the Sprint Goal.

[Scrum Guide], section 2.2: ''The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required.''

Accountabilities in Scrum | Scrum.org: ''Scrum has three accountabilities, each with a different focus : Product Owner (green figure) The 'What'. With a focus on Value, time to market, return on investment and Total Cost of Ownership (TCO). Developers (red figures) The 'How'. Focus on building something that is Done -- that the increment is useable and potentially releasable.''

What is a Developer in Scrum? | Scrum.org: ''The specific skills needed by the Developers are often broad and will vary based on the type of work they are doing. However, the Developers are always accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward the Sprint Goal''

The Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that 'The Developers are required to conform to the Definition of Done, as defined by the Scrum Team.If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.'1This means that the Product Owner does not have the final say over the Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.

1: The Scrum Guide2, page 14

2:The Scrum Guide

The Daily Scrum is held at the same time and same place because:

The consistency reduces complexity. By having a fixed time and place for the Daily Scrum, the Developers can avoid wasting time and energy on scheduling, logistics, or coordination issues. They can also establish a routine and a rhythm that helps them focus on their work and their Sprint Goal.

The consistency increases transparency. By having a fixed time and place for the Daily Scrum, the Developers can ensure that everyone is aware of when and where the meeting takes place, and that everyone has an opportunity to participate and share their progress, plans, and challenges. They can also invite other stakeholders or observers, if they find it useful, to provide feedback or support.

The consistency enhances collaboration. By having a fixed time and place for the Daily Scrum, the Developers can create a safe and comfortable space for them to communicate, interact, and collaborate with each other. They can also build trust, rapport, and accountability among themselves, and foster a sense of team spirit and ownership.

Scrum Guide 2020, page 12: ''The Daily Scrum is held at the same time and place each day to reduce complexity.''

Scrum Guide 2020, page 12: ''The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.''

Scrum Guide 2020, page 13: ''The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.''

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.

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.''