The correct answer is to split the large user stories into smaller, more specific stories with acceptance criteria. This is because agile methodologies require user stories to be estimable and actionable within a single sprint, directly aligning with the INVEST principle—where the 'S' stands for Small and the 'T' for Testable. Vague, oversized stories violate the 'Estimable' criterion, making sprint planning impossible. On the CAPM exam, this scenario tests your understanding of agile requirements refinement, often appearing as a trap where candidates might mistakenly choose to add more detail to the existing story or reorder the backlog instead of splitting. Remember that refinement is about breaking down epics, not just rewriting them. A useful memory tip is the "SPIDR" technique for splitting stories: by Spike, Path, Interface, Data, or Rules—ensuring each resulting story is small enough to fit a sprint and has clear acceptance criteria.
CAPM Business Analysis Frameworks Practice Question
This CAPM practice question tests your understanding of business analysis frameworks. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A business analyst is working on a project to develop a mobile banking application. During the requirements analysis phase, the BA creates a set of user stories and acceptance criteria. The BA then conducts a peer review with the development team. The team points out that the stories are too large and vague to estimate. The BA needs to refine the requirements to make them actionable. The project is using an agile methodology with two-week sprints. What should the BA do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Split the large user stories into smaller, more specific stories with acceptance criteria.
In agile methodologies, user stories must be small enough to fit within a single sprint and provide clear, testable acceptance criteria for estimation and development. Splitting large, vague stories into smaller, specific stories with acceptance criteria directly addresses the team's inability to estimate, enabling accurate sprint planning and incremental delivery. This aligns with the INVEST principle (Independent, Negotiable, Valuable, Estimable, Small, Testable) for effective user stories.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Split the large user stories into smaller, more specific stories with acceptance criteria.
Why this is correct
Splitting stories makes them estimable and sprint-ready.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add more detail to the existing user stories and acceptance criteria.
Why it's wrong here
More detail doesn't reduce story size; stories need to be split.
✗
Create a prototype to clarify requirements and then rewrite stories.
Why it's wrong here
Prototyping helps but is not the primary solution for oversized stories.
✗
Ask the development team to re-estimate the stories as they are.
Common exam trap: answer the scenario, not the keyword
PMI often tests the misconception that adding more detail or creating a prototype is sufficient to make stories actionable, but the core agile requirement is that stories must be small enough to be estimable and completed within a single sprint.
Detailed technical explanation
How to think about this question
Under the hood, agile estimation techniques like Planning Poker rely on story points relative to a baseline story; if stories are too large (epics), they break the Fibonacci scale and cause wide variance in estimates. In real-world mobile banking projects, a story like 'User can manage accounts' must be decomposed into atomic stories such as 'User can view account balance' and 'User can transfer funds between accounts', each with specific acceptance criteria like 'Given a user is authenticated, when they select transfer, then they see a form with source and destination account fields'. This granularity allows developers to assign story points (e.g., 3 or 5) that fit within a sprint's velocity.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the CAPM exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Business Analysis Frameworks — This question tests Business Analysis Frameworks — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Split the large user stories into smaller, more specific stories with acceptance criteria. — In agile methodologies, user stories must be small enough to fit within a single sprint and provide clear, testable acceptance criteria for estimation and development. Splitting large, vague stories into smaller, specific stories with acceptance criteria directly addresses the team's inability to estimate, enabling accurate sprint planning and incremental delivery. This aligns with the INVEST principle (Independent, Negotiable, Valuable, Estimable, Small, Testable) for effective user stories.
What should I do if I get this CAPM question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.