easyMultiple Choice
PK0-005 Practice Question: A project manager is assigned to a project that…
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?
⚠ Common exam trap
Watch out — candidates often choose Waterfall because they associate it with 'structured' project management, failing to recognize that Agile is specifically designed to manage uncertainty and changing requirements through iterative delivery.
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 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.
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 suits poorly defined requirements because it delivers work in short iterations, letting the team refine scope as understanding grows. Rather than fixing requirements upfront, iterative planning and continuous stakeholder feedback absorb uncertainty, satisfying the stem's core constraint: requirements that cannot be specified in advance.
- ✗
Waterfall
Why it's wrong here
Waterfall fixes requirements and scope before build begins, so poorly defined requirements force costly late rework. It is tempting because it offers clear sequential governance and documentation, and it works well when requirements are stable and well understood from the outset.
- ✗
Six Sigma
Why it's wrong here
Six Sigma reduces process variation and defects using DMAIC, assuming measurable, stable processes rather than undefined product scope. It is tempting as a structured improvement method, but it addresses quality of existing processes, not discovery of unknown requirements. An iterative, incremental approach suits uncertainty.
- ✗
PRINCE2
Why it's wrong here
PRINCE2 relies on defined requirements and stage boundaries to authorise work, so poorly defined scope undermines its product-based planning. It is tempting because PRINCE2 tolerates change via tolerances, but it still requires a baseline. An iterative methodology that embraces evolving requirements would fit.
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 →
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.