According to the Agile Practice Guide and the Scrum Guide, Scrum artifacts are designed to provide transparency and opportunities for inspection and adaptation.

The Sprint Backlog: This is a set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. It is highly specific to the current iteration (Sprint). Only the items the team commits to finishing within the timebox are included here.

Ownership: While the Product Owner prioritizes the Product Backlog, the Developers (the Team) own the Sprint Backlog. They decide how much work they can realistically pull into the sprint and how that work will be accomplished.

Analysis of other options:

Option A: This is incorrect. The Product Backlog is, by definition, an ordered (prioritized) list of everything that is known to be needed in the product.

Option C: This is a common distractor. The Product Owner prioritizes the Product Backlog. However, the Sprint Backlog is created by the team during Sprint Planning. While it contains items the Product Owner has prioritized, it is defined by its focus on the " current sprint, " making Option B a more precise definition of the artifact ' s purpose.

Option D: This is backwards. The Sprint Backlog is a subset of the Product Backlog, not the other way around. The Product Backlog represents the " Big Picture, " while the Sprint Backlog is the " Immediate Work. "

Key Differences at a Glance:

Per PMI standards and Scrum principles, the Sprint Backlog serves as a visible, real-time picture of the work that the Developers plan to accomplish during the Sprint to achieve the Sprint Goal.