C: The Scrum Guide defines Scrum as "a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems." This is a core truth.

D: Scrum’s foundation in empirical process control theory (transparency, inspection, adaptation) is explicitly stated in the Scrum Guide : "Scrum is founded on empiricism and lean thinking."

As Scrum Teams mature, they improve quality and effectiveness. The Scrum Guide implies that the Definition of "Done" evolves: "As Scrum Teams mature, it is expected that their definitions of ‘Done’ will expand to include more stringent criteria for higher quality."

A: Events remain mandatory for Scrum’s structure.

B: The Scrum Master remains vital for coaching and facilitation.

The Scrum Guide defines the Product Owner as "accountable for maximizing the value of the product resulting from the work of the Scrum Team." Option B (Value optimizer) encapsulates this core focus on value delivery. Option A (Requirements engineer) is too narrow—while they manage requirements, their role transcends engineering to strategic vision. Option C (Team manager) is incorrect—they don’t manage the team; the Scrum Master supports team self-management. Option D (Go-between) understates their authority; they actively shape the product, not just relay information. Thus, B is the best description.

The Scrum Guide requires transparency but doesn’t mandate specific tools: "The Product Owner is accountable for... ensuring that the Product Backlog is transparent, visible, and understood." Progress tracking is necessary, but the method is flexible.

D: This allows any trend-based practice (e.g., burn-downs, burn-ups), fitting Scrum’s adaptability.

A, B: Useful but not mandatory; Scrum doesn’t prescribe them.

C: Gantt charts are traditional, not Scrum-aligned.

Self-organization gives the Developers autonomy over their work execution, but not over Product Backlog ordering, which is the Product Owner’s domain. The Scrum Guide states: "The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."

A: Pulling items into the Sprint Backlog is their responsibility during Sprint Planning.

B: Reordering the Product Backlog is the Product Owner’s task: "Ordering Product Backlog items."

C: Delivering "Done" work is their core duty.

The Scrum Master ensures the Daily Scrum is effective, with a key focus on its 15-minute time-box. The Scrum Guide states: "The Scrum Master teaches the Developers to keep it within the 15-minute timebox." While they may support other aspects, managing the time-box is primary when present.

A: Correct—time-box adherence is key.

B: The three questions are a practice, not mandatory; Developers run the event.

The Product Backlog is managed solely by the Product Owner, not stakeholders. The Scrum Guide explains: "The Sprint Review is a working session... The Product Owner discusses the Product Backlog as it stands." Stakeholders provide feedback during the Sprint Review, which the Product Owner may use to adjust priorities, but they don’t directly re-prioritize it.

A: False—stakeholders don’t have this authority.

The Scrum Guide states that the Sprint Backlog is owned by the Developers, who are responsible for planning and executing the work to achieve the Sprint Goal. If they realize they’ve over-committed, they must adjust the Sprint Backlog. However, since the Product Owner is accountable for maximizing value and managing the Product Backlog, their involvement is critical to ensure adjustments align with value delivery and the Sprint Goal. The Scrum Guide notes: "The Product Owner may influence the Developers by helping them understand and select trade-offs." Option A includes a non-existent "project manager" role in Scrum, making it incorrect. Option C involves stakeholders, who are not part of mid-Sprint adjustments (they provide feedback at the Sprint Review). Option D excludes the Product Owner, which is insufficient given their role. Thus, B is correct.

Scrum defines three roles: Product Owner, Scrum Master, and Developers. The Scrum Guide states: "The Scrum Team consists of one Scrum Master, one Product Owner, and Developers." Project Manager (C) is a traditional role absent in Scrum, where responsibilities are distributed among the Scrum Team.

A, B, D: These are explicit Scrum roles.

The Definition of "Done" ensures quality and usability, critical for the Product Owner’s value delivery:

A: Per the Scrum Guide , a "Done" Increment is usable, enabling the Product Owner to decide on releases at the Sprint Review.