Commit User Stories
The Scrum Team agrees to deliver the Product Owner-approved user stories in the upcoming Sprint, producing a clear set of committed user stories.
Key Points
- Happens during Sprint Planning after the Product Owner confirms which user stories are ready and prioritized.
- The team selects stories based on capacity, velocity, and Definition of Done to create a realistic Sprint scope.
- Results in a Sprint Backlog containing the committed user stories and initial implementation plan.
- Commitment is a team agreement to deliver; scope may still be refined as learning occurs during the Sprint.
Example
In Sprint Planning, the Product Owner presents the top backlog items with clear acceptance criteria. The developers discuss capacity, estimate effort, and select five user stories they can complete. They move these items into the Sprint Backlog and record them as the committed user stories for the Sprint.
PMP Example Question
During Sprint Planning, which activity creates a definitive set of user stories the team agrees to deliver in the Sprint?
- Define Acceptance Criteria
- Commit User Stories
- Backlog Refinement
- Sprint Review Preparation
Correct Answer: B — Commit User Stories
Explanation: Commit User Stories is when the team agrees to deliver Product Owner-approved stories for the Sprint, forming the Sprint Backlog.
