CAPM Agile Frameworks and Methodologies Practice Question
A product owner is writing user stories for a new feature. Which of the following is a best practice for ensuring the stories are well-formed?
⚠ Common exam trap
CAPM often tests the misconception that 'well-formed' means documentation or ownership (single doc, assigned developer) rather than the INVEST criteria, so candidates pick A or B instead of recognizing the 'Small' requirement.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Ensure each story is small enough to complete in one sprint
In agile practice, a well-formed user story must satisfy the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). The 'Small' criterion requires that a story be sized so it can be completed within a single sprint iteration; this keeps feedback loops short, enables reliable velocity tracking, and prevents stories from becoming de facto epics. Stories that span multiple sprints cannot be marked 'Done' at sprint review, which breaks the transparency and empiricism Scrum depends on.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Store all stories in a single document for traceability
Why it's wrong here
A single document cannot support backlog ordering, splitting or INVEST criteria checks, and it becomes stale as priorities shift each sprint. It is tempting because one document feels traceable, and it would be correct for a requirements specification or contract baseline rather than a living product backlog.
- ✗
Assign each story to a specific developer for ownership
Why it's wrong here
Assigning a story to one developer discourages collective ownership and swarming, and it does not test whether the story is independent, negotiable, valuable, estimable, small and testable. It is tempting because named ownership clarifies accountability, and it is correct for tracking a task or defect rather than shaping a user story.
- ✗
Write stories after the sprint starts to ensure accuracy
Why it's wrong here
Writing stories after the sprint begins removes the backlog refinement and team estimation that expose ambiguity, so defects surface mid-sprint. It is tempting because late writing feels responsive to new information, and it would suit emergent, spike-driven discovery work where scope is genuinely unknown until investigation starts.
- ✓
Ensure each story is small enough to complete in one sprint
Why this is correct
Sizing each story to fit within a single sprint keeps it independently deliverable and testable, satisfying the INVEST criterion of small size. This directly addresses the stem's best-practice requirement for well-formed stories, preventing stories that sprawl across iterations and stall feedback.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAPM exam.