Courseiva
Process — Managing Technical AspectsmediumMultiple ChoiceObjective-mapped

PMP Process — Managing Technical Aspects Practice Question

During a sprint planning meeting, the product owner wants to add a high-priority user story that the team believes is too large to complete in one sprint. What should the team do?

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

Work with the product owner to break the story down into smaller, manageable pieces

The team should collaborate with the product owner to decompose the large user story into smaller, manageable pieces that can be completed within a single sprint. Option A is wrong because accepting a story that is too large and working overtime leads to burnout and poor quality. Option B is wrong because having the product owner attend daily standups does not solve the sizing issue. Option D is wrong because outright refusal is not collaborative; the team should work with the product owner to find a solution.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Accept the story and work overtime to complete it

    Why it's wrong here

    Agile principles emphasize a sustainable pace and predictable delivery, making planned overtime an unsustainable practice. Accepting an oversized story and immediately resorting to overtime indicates a failure in proper sprint planning and a disregard for the team's long-term well-being and productivity. This approach often leads to burnout, decreased quality, and ultimately undermines the team's ability to deliver consistently and predictably.

  • Ask the product owner to attend the daily standups for this sprint only

    Why it's wrong here

    While a Product Owner's presence at daily standups can certainly foster communication and help clarify ongoing impediments, it fundamentally does not address the core issue of an oversized user story during sprint planning. The purpose of sprint planning is to ensure stories are "ready" and appropriately sized for the sprint, which is a proactive measure. Attending standups might provide reactive clarification but won't magically break down a large story into sprint-sized chunks or make it fit the sprint capacity.

  • Work with the product owner to break the story down into smaller, manageable pieces

    Why this is correct

    This is the most appropriate and collaborative agile response. During sprint planning, if a user story is deemed too large to fit within the sprint's capacity, the development team must work directly with the Product Owner to refine and split it into smaller, independent, valuable, and estimable user stories. This ensures the work is manageable, maintains a sustainable pace, and allows for incremental delivery and valuable feedback within the sprint.

  • Refuse to accept the story because it is too large

    Why it's wrong here

    Simply refusing a user story outright without engaging in collaborative problem-solving is counterproductive and goes against the foundational principles of agile teamwork. The development team and Product Owner are expected to work together to achieve sprint goals and refine the product backlog. A direct refusal without attempting to decompose or refine the story fails to leverage the collective intelligence and problem-solving capabilities inherent in a high-performing scrum team.

About these practice questions

Courseiva writes every PMP question from scratch — 800 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This PMP 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 PMP exam.