hardMultiple Choice
When to Use Agile Methodology
A project manager is assigned to a project that has a high degree of uncertainty and rapidly changing requirements. The project sponsor is concerned about cost overruns and wants a method that allows for frequent delivery of value while adapting to changes. Which project management methodology should the project manager recommend?
Quick Answer
Agile is the correct choice because it is specifically designed to handle high uncertainty and rapidly changing requirements through iterative development and adaptive planning. This methodology directly addresses the sponsor’s cost concerns by enabling frequent delivery of value and allowing scope and priorities to shift based on ongoing feedback, rather than locking in a fixed plan upfront. On the CompTIA Project+ PK0-005 exam, this scenario tests your ability to match methodology characteristics to project constraints—Agile is the go-to when requirements are fluid and stakeholder collaboration is high, while Waterfall is a common trap for those who default to rigid planning. A helpful memory tip is to think of the word “ADAPT”: Agile Delivers Adaptive, Progressive, and Timely value, which fits projects where change is the only constant.
⚠ Common exam trap
CompTIA often tests the misconception that PRINCE2 is adaptive like Agile, but PRINCE2's stage-gate controls and emphasis on upfront planning make it less suitable for rapidly changing requirements than Agile's iterative approach.
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
✓
Agile
Agile is the correct methodology because it is designed for projects with high uncertainty and rapidly changing requirements. It emphasizes iterative development, frequent delivery of value, and adaptive planning, which directly addresses the sponsor's concerns about cost overruns by allowing the team to adjust scope and priorities based on feedback.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Agile
Why this is correct
Agile's iterative, incremental delivery cycles accommodate rapidly changing requirements while producing working value frequently, addressing the sponsor's cost-overrun concern through early, continuous feedback. Predictive waterfall approaches fix scope upfront, which suits stable requirements rather than the high uncertainty described in the stem.
- ✗
Six Sigma
Why it's wrong here
Six Sigma reduces process variation in stable, repeatable operations; it offers no cadence for delivering value under shifting requirements. It is tempting because its cost-saving reputation addresses the sponsor's overrun concern, but DMAIC assumes a defined process, not emergent scope.
- ✗
PRINCE2
Why it's wrong here
PRINCE2 is a stage-gated governance method with defined products and stage boundaries, so it accommodates change through formal exception and change control rather than frequent incremental delivery. It is tempting for its cost tolerance controls, but iterative adaptive delivery needs an agile approach.
- ✗
Waterfall
Why it's wrong here
Waterfall fixes scope and schedule up front, so it cannot absorb rapidly changing requirements without costly re-baselining at each phase gate. It suits projects with stable, well-understood requirements and regulatory stage approvals, where sequential delivery is acceptable.
Go deeper
Related to this question
About these practice questions
This PK0-005 question is part of Courseiva's 954-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on PK0-005
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A project manager is assigned to a project that has poorly defined requirements. Which project management methodology would be most suitable to handle this uncertainty?
easy- ✓ A.Agile
- B.Waterfall
- C.Six Sigma
- D.PRINCE2
Why A: Agile is the most suitable methodology for projects with poorly defined requirements because it embraces iterative development, continuous feedback, and adaptive planning. Unlike rigid, sequential approaches, Agile allows the project team to refine requirements incrementally through short sprints and regular stakeholder collaboration, making it ideal for managing uncertainty.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PK0-005 practice question is part of Courseiva's free CompTIA 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 PK0-005 exam.