CAPM Practice: Explain when it is appropriate to use an adaptive approach
Question 45 of 61 in Explain when it is appropriate to use an adaptive approach
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: User stories describe the what and why; acceptance criteria define testable conditions that must be met for the story to be accepted
Explanation
User stories capture WHAT is needed and WHY ('As a [user], I want [functionality] so that [benefit]'). Acceptance criteria define specific, testable conditions that must be true for the story to be considered complete. Acceptance criteria translate the user's need into verifiable outcomes — they're the criteria the team and product owner use to agree that work is done.
**Why not A:** User stories are not technical specifications — they are written from the user's perspective in business terms. Acceptance criteria are not a separate set of business requirements; they are the testable conditions attached to a specific story.
**Why not C:** Neither artifact belongs to a single role. User stories are typically owned by the product owner and refined collaboratively with the team, and acceptance criteria are agreed between the product owner and the team rather than written by testers alone.
**Why not D:** User stories and acceptance criteria are complementary, not interchangeable. The story expresses the need and its value, while the acceptance criteria specify the verifiable conditions that confirm the story is done.
Key Concept
This question covers Explain when it is appropriate to use an adaptive approach under Explain when it is appropriate to use an adaptive approach (Agile Frameworks/Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free