PK0-005 Project Management Concepts Practice Question
A project manager is assigned to a new software development project. The requirements are well understood and unlikely to change. Which project management methodology is most appropriate for this project?
⚠ Common exam trap
PK0-005 often tests the misconception that Agile is always the best choice for any software project, but the key differentiator is requirement stability; when requirements are well understood and unlikely to change, predictive is more appropriate.
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
✓
Predictive
Predictive (waterfall) methodology is correct because it relies on detailed upfront planning and sequential execution, which works best when requirements are stable and well understood. Since the project has clear, unchanging requirements, the predictive approach minimizes risk and provides a structured, predictable path to completion. Agile and Scrum are designed for evolving requirements and iterative feedback, which are unnecessary here and could introduce inefficiency.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Hybrid
Why it's wrong here
Hybrid mixes predictive and adaptive elements, so it still introduces iterative planning and feedback loops that stable, fully understood requirements do not need. It is tempting because hybrid suits projects with some uncertainty in part of the scope, which would make it the right pick when only portions of the requirements are fixed.
- ✗
Scrum
Why it's wrong here
Scrum delivers work in fixed-length sprints with a product backlog refined each iteration, which adds overhead when requirements are already settled and unlikely to change. It is tempting because Scrum excels where scope emerges through frequent stakeholder feedback, making it correct for projects with evolving or unclear requirements.
- ✗
Agile
Why it's wrong here
Agile embraces changing requirements through short iterations and continuous reprioritisation, which is unnecessary when scope is stable and well understood. It is tempting because Agile is widely adopted and works well for exploratory or customer-driven work, making it the right choice when requirements are expected to shift during delivery.
- ✓
Predictive
Why this is correct
Predictive methodology suits this project because stable, well-understood requirements allow full scope definition upfront, enabling sequential phase planning, detailed baselines and formal change control. Its plan-driven structure minimises rework where change is unlikely, unlike adaptive approaches that assume evolving requirements and iterative discovery.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.