PMI-ACP Practice Question: A project is failing to deliver value because the features are too large
A project is failing to deliver value because the features are too large. What is the recommended strategy?
⚠ Common exam trap
PMI-ACP often tests the misconception that large features are acceptable if the team works harder or adds resources, when the agile-correct answer is to decompose them into smaller, value-delivering increments.
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
✓
Decompose epics into smaller, investable user stories.
When features are too large to deliver value, the recommended agile strategy is to decompose epics into smaller, investable user stories that can be completed and delivered incrementally. Smaller stories enable faster feedback, reduce risk, and allow the team to deliver value continuously rather than in large, infrequent batches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Stop the project.
Why it's wrong here
Cancelling discards the product investment instead of addressing feature granularity, which slicing into smaller increments solves while preserving value delivery. Stopping is tempting when value is absent, and would be right if the product itself were obsolete or unfundable rather than merely oversized.
- ✓
Decompose epics into smaller, investable user stories.
Why this is correct
Large features delay feedback and obscure value delivery. Splitting epics into smaller, investable user stories shortens the feedback loop, letting the team deliver and validate increments frequently, directly addressing the stem's root cause of oversized features.
- ✗
Hire more testers.
Why it's wrong here
Adding testers expands verification capacity but leaves feature size unchanged, so the value bottleneck persists. Scaling QA is tempting because large features strain testing, and would be correct if defects or regression coverage, not increment size, were blocking delivery.
- ✗
Keep the features large to avoid complexity.
Why it's wrong here
Retaining large features perpetuates the batch size that suppresses feedback and delays value, the opposite of the required decomposition. Preserving scope is tempting as risk avoidance, and would suit a fixed-price contractual deliverable where scope cannot legally be split.
About these practice questions
Courseiva writes every PMI-ACP question from scratch — 244 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 →
You might also like
Similar PMI-ACP questions
- A team is using a WIP (Work In Progress) limit of 3 on their 'Testing' column. A developer moves a fourth item into 'Tes…
- Which of the following is an effective way to prioritize a product backlog based on organizational goals?
- Which THREE techniques help minimize context switching?
- Which THREE metrics should a practitioner focus on to measure end-to-end delivery performance?
- During a sprint planning session, the team realizes that the current sprint backlog contains items with significantly hi…
Written and reviewed by Johnson Ajibi, MSc IT Security
Security Systems Architect · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
This PMI-ACP 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 PMI-ACP exam.