Question 8 of 503
Agile Frameworks and MethodologiesmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to collaboratively break down the story into smaller, sprint-sized stories. This is because in Scrum, a user story that is too large for a single Sprint is classified as an epic, and the entire team—Product Owner and Developers—must decompose it during Sprint Planning to ensure each piece fits within the timebox and supports the Sprint Goal. The CAPM exam tests your understanding of the Scrum Guide’s emphasis on self-organization and sustainable pace, often presenting a trap where you might think the Product Owner should work alone or defer the story. Instead, remember that decomposition is a team activity done right in the planning meeting. A useful memory tip: “If it’s too big to sprint, break it into bits—teamwork makes the backlog fit.”

CAPM Agile Frameworks and Methodologies Practice Question

This CAPM practice question tests your understanding of agile frameworks and methodologies. 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.

During Sprint Planning, the Product Owner proposes a user story that is too large to fit in one Sprint. What should the team do?

Question 1mediummultiple choice
Full question →

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

Collaboratively break down the story into smaller, sprint-sized stories.

In Scrum, user stories that are too large (often called 'epics') must be decomposed into smaller, sprint-sized stories during Sprint Planning. The Product Owner and Development Team collaboratively break down the story to ensure each piece can be completed within a single Sprint, maintaining the Sprint Goal and timebox. This aligns with the Agile principle of sustainable pace and the Scrum Guide's emphasis on the Development Team's self-organization to determine how to deliver the Product Backlog items.

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.

  • Collaboratively break down the story into smaller, sprint-sized stories.

    Why this is correct

    Decomposition is a standard Agile practice.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Reject the story and ask for a smaller one.

    Why it's wrong here

    The team should collaborate to break it down.

  • Accept the story and work overtime to complete it.

    Why it's wrong here

    Overtime is not a sustainable practice in Agile.

  • Accept the story and commit to completing it in the Sprint.

    Why it's wrong here

    Overcommitting leads to failure and demotivation.

Common exam traps

Common exam trap: answer the scenario, not the keyword

PMI often tests the misconception that the Product Owner alone decides story size or that the team should simply reject or accept oversized stories, but the correct Scrum practice is collaborative decomposition during Sprint Planning.

Detailed technical explanation

How to think about this question

Under the hood, user stories are sized using relative estimation techniques like story points, and an epic typically exceeds the team's velocity for a single Sprint. During Sprint Planning, the team applies the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) to ensure stories are sprint-sized. In a real-world scenario, a team might use a 'Sprint 0' or backlog refinement session to decompose epics before Sprint Planning, but if encountered during planning, the team must immediately break it down to avoid scope creep and maintain the Sprint timebox.

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.

Related practice questions

Related CAPM practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free CAPM practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this CAPM question test?

Agile Frameworks and Methodologies — This question tests Agile Frameworks and Methodologies — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Collaboratively break down the story into smaller, sprint-sized stories. — In Scrum, user stories that are too large (often called 'epics') must be decomposed into smaller, sprint-sized stories during Sprint Planning. The Product Owner and Development Team collaboratively break down the story to ensure each piece can be completed within a single Sprint, maintaining the Sprint Goal and timebox. This aligns with the Agile principle of sustainable pace and the Scrum Guide's emphasis on the Development Team's self-organization to determine how to deliver the Product Backlog items.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More CAPM practice questions

Last reviewed: Jun 30, 2026

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.

Loading comments…

Sign in to join the discussion.

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.