A product owner obtains customer confirmation on product requirements and provides them to the team. After explaining the user stories, the product owner receives agreement for acceptance from the…

Question

Options

• AUse agile estimation techniques to create a shared understanding of when the user stories will be
• BAgree upon development and testing activities for the user stories.
• CComplete the user stories, and provide a demo for the product owner and customer.
• DComplete the user stories, and hold a retrospective to discuss them.

• A
  5% (2)
• B
  8% (3)
• C
  72% (28)
• D
  15% (6)

Explanation

The sequence described - customer confirms requirements, product owner explains stories, team agrees on acceptance criteria - represents the end of planning and the start of execution. The logical next step is to complete the user stories through development and testing, then demonstrate the working product to the product owner and customer for validation. This demo (sprint review) closes the feedback loop with the customer. Option A (estimation) and B (agreeing on activities) are planning steps that would have occurred before this point. Option D replaces the customer demo with a retrospective, skipping the critical stakeholder validation step.

No community discussion yet for this question.