Exam CAPM topic 1 question 299 discussion

In adaptive (Agile) projects, when grooming (refining) the backlog, it's essential for the team to understand what "done" means for each user story. This is where detailed acceptance criteria come into play.

Why other options are less relevant for determining work needed: A. Team velocity in past iterations: ❌ Helps forecast how much work the team can handle but does not define what work is needed for individual stories. B. Related epics of each story: ❌ Provides context and grouping but doesn’t specify the tasks or work needed for the story itself. D. Product owner’s priorities: ❌ Important for ordering the backlog but does not help specify the work involved in completing a story.

C. Detailed acceptance criteria Explanation: To accurately determine the work needed to complete a user story and ensure everyone understands the requirements, detailed acceptance criteria are essential. They provide clear and specific conditions that must be met for the user story to be considered complete. Team velocity is a metric used to estimate the amount of work a team can complete in a sprint, but it doesn't help define the work for a specific user story. Related epics provide context but don't outline specific tasks. While the product owner's priorities are important for determining the order of work, they don't define the work itself. By having clear acceptance criteria, the team can break down the user story into tasks, estimate effort, and plan the work for the iteration.