CAPM Practice Question: Project Management Fundamentals and Core Concepts
Your organization is initiating a new mobile app development project. The product owner expects to release a minimum viable product (MVP) within three months, with subsequent iterations based on user feedback. The development team is experienced with agile methodologies. The project sponsor, however, is accustomed to traditional waterfall projects and insists on a detailed upfront plan covering all requirements and a fixed schedule. You need to select a project life cycle that balances the product owner's desire for iterative delivery with the sponsor's need for predictability. What is the most appropriate approach?
⚠ Common exam trap
CAPM often tests the misconception that you must choose either pure waterfall or pure agile, when hybrid or iterative approaches are valid and often preferred for balancing stakeholder needs.
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
✓
Use an iterative life cycle with a high-level plan and regular releases
An iterative life cycle with a high-level plan and regular releases balances the product owner's need for iterative delivery (MVP and feedback-driven iterations) with the sponsor's need for predictability (high-level roadmap and scheduled releases). This hybrid approach provides enough upfront planning to satisfy the sponsor while allowing flexibility for agile execution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Combine agile and waterfall by using waterfall for planning and agile for execution
Why it's wrong here
Waterfall planning freezes all requirements before development starts, so agile execution cannot absorb feedback without invalidating the baseline the sponsor approved. It is tempting as a hybrid compromise, and would work where scope is genuinely fixed but delivery cadence is uncertain, not where iterative discovery drives the product.
- ✓
Use an iterative life cycle with a high-level plan and regular releases
Why this is correct
An iterative life cycle delivers working increments each iteration while a high-level plan gives the sponsor predictable milestones and release cadence. This balances the product owner's feedback-driven MVP with the sponsor's need for upfront visibility, unlike pure predictive or fully adaptive approaches.
- ✗
Use a pure agile approach with no upfront planning beyond the MVP
Why it's wrong here
Pure agile abandons the fixed schedule and upfront requirements baseline the sponsor needs, so predictability is unmet. It fits stable, co-located teams with engaged stakeholders and no external date commitments, where scope flexes freely across iterations.
- ✗
Use a waterfall life cycle to create a detailed plan as the sponsor wants
Why it's wrong here
Waterfall fixes scope and schedule upfront, so the MVP cannot be reshaped by user feedback after each iteration, breaking the product owner's requirement. It is tempting because the sponsor's demand for a detailed plan and predictable dates is exactly what waterfall delivers, and it would suit a project with stable, fully known requirements.
Go deeper
Related to this question
About these practice questions
One of 451 original CAPM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.