When a team reports that user stories are unclear or lack sufficient detail, the correct agile response is to foster collaborative refinement and shared understanding. A user story workshop is a well-recognized practice that involves the team and product owner collaborating to write, clarify, and refine stories. This is supported by the PMI Agile Practice Guide (Section 5.2: User Stories and Backlog Refinement), which recommends story-writing workshops as a proactive way to clarify requirements.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) notes that good agile teams collaboratively refine stories in grooming sessions or workshops to ensure shared clarity and alignment.
Option C is correct: a workshop enables both the team and product owner to collaborate in improving story clarity.
Option A oversimplifies the solution—acceptance criteria alone don’t fully define a story.
Option B misuses the retrospective, which is for process improvement, not story editing.
Option D escalates prematurely and undermines team ownership and collaboration.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit