TheScrum Guidetasks the Product Owner with ordering the Product Backlog to maximize value, but it doesn't mandate a specific method like "value points." Option B is correct-using value points (e.g., in techniques like WSJF-Weighted Shortest Job First) is a helpful practice, but empirical validation (market reception) remains the ultimate measure, aligning with Scrum's focus on inspection and adaptation. Option A overstates value points as "ultimate," ignoring real-world feedback. Option C is too rigid; Scrum allows flexibility in tools as long as empiricism is upheld. Thus, B is the best answer.

The Developers own the Sprint Backlog and update it as work progresses. TheScrum Guidestates: "The Sprint Backlog is a plan by and for the Developers... As new work is required, the Developers add it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated."
* A:The Scrum Master facilitates, not updates.
* B:Correct-the Developers manage it.

Scrum does not mandate specific tools like burndown charts; it focuses on outcomes (e.g., a "Done" Increment) rather than prescriptive practices. TheScrum Guidementions progress tracking as optional:
"Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism."
* A:False-burndown charts are optional.

The Definition of "Done" is a shared standard, often set by the organization, but defaults to the Scrum Team if no broader standard exists. TheScrum Guidestates: "If the Definition of Done for an increment is part of the conventions, standards, or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product."
* A:Correct-organizational standards take precedence, otherwise the Scrum Team defines it.
* B:Collaboration occurs, but it's not just a "common denominator."

The Sprint Goal and the Sprint Backlog are both outcomes of Sprint Planning, making this statement true.
According to theScrum Guide, Sprint Planning is an event where the Scrum Team collaborates to define the work to be performed during the Sprint. The Sprint Goal is a single objective set for the Sprint, providing focus and coherence to the work selected. It is crafted collaboratively by the Product Owner, Developers, and Scrum Master during Sprint Planning. Simultaneously, the Sprint Backlog is created, consisting of the Product Backlog items selected for the Sprint plus a plan to deliver them, aligned with the Sprint Goal. The Scrum Guidestates: "Sprint Planning initiates the Sprint by laying out the work to be performed... This resulting plan is created by the collaborative work of the entire Scrum Team." Thus, both the Sprint Goal and Sprint Backlog emerge from this event, confirming option A as correct.