How should Scrum teams plan work to be performed within Sprints?

Scrum teams plan workone Sprint at a time, using theSprint Planning eventto adapt the Sprint Backlog based on what was learned in previous Sprints. This approach aligns with Scrum'sempirical process control, which relies on inspection and adaptation to plan effectively.

According to the2020 Scrum Guide:

Sprint Planning creates aSprint Backlog, which includes the Sprint Goal, selected Product Backlog items, and the plan to deliver them.

Teams adjust their plans Sprint by Sprint, responding to new information, feedback, and changing circumstances.

Why the other options are incorrect:

A. One release at a time, adjusting the number of Sprints to the prior releases’ average velocity:Scrum does not prescribe release-driven planning or adjusting Sprint duration based on velocity.

C. One project at a time, adjusting each Sprint Backlog Item to meet the release date negotiated at inception:Scrum encourages iterative planning within Sprints, not fixed plans tied to predetermined release dates.

D. One Sprint at a time in the Product Backlog Refinement meeting with participation of stakeholders:Product Backlog Refinement is an ongoing activity, not a Sprint planning process. Stakeholders typically participate in Sprint Reviews, not in backlog refinement.