Sprint planning should result in a commitment on what will be delivered at the end of the Sprint. Who makes this commitment?

Question

Options

• AThe Product Owner
• BThe Scrum Master
• CThe team

• A
  5% (2)
• B
  5% (2)
• C
  89% (33)

Explanation

In Scrum, the Development Team (the team) makes the commitment during Sprint Planning because they are the ones who will actually do the work - only they can realistically assess what is achievable within the Sprint timebox. The Product Owner (A) prioritizes and owns the backlog but cannot commit on behalf of the people doing the work; imposing a commitment on the team would undermine self-organization. The Scrum Master (B) is a facilitator and servant-leader, not a decision-maker on delivery scope. A helpful memory tip: think "those who do the work, make the commitment" - just as you wouldn't promise a deadline on a colleague's behalf, the team alone owns what they can deliver.

No community discussion yet for this question.