FC0-U71 Software Development Concepts Practice Question
A software development team is adopting agile practices. Which TWO of the following are common characteristics of agile methodologies? (Select TWO.)
⚠ Common exam trap
The trap is that some options sound like general good practices (e.g., documentation, fixed scope) but are actually antithetical to agile principles; candidates may select them if they confuse agile with disciplined project management.
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
✓
Iterative development with short cycles
Option B is correct because agile methodologies, such as Scrum and Extreme Programming, deliver work in short, repeating iterations (typically 1–4 week sprints) that produce a potentially shippable increment each cycle, rather than progressing through one long sequential pass. Option C is correct because it reflects one of the four values in the Agile Manifesto, which explicitly states a preference for 'responding to change over following a plan,' allowing teams to adapt scope and priorities as requirements evolve. Option A is incorrect because sequential phases (requirements→design→implementation) describe the waterfall model, which agile explicitly contrasts with its iterative and incremental approach. Option D is incorrect because agile embraces emergent and evolving scope rather than fixing the full scope at the start, which is characteristic of plan-driven/waterfall contracts. Option E is incorrect because agile values 'working software over comprehensive documentation,' favoring lightweight, just-enough documentation over exhaustive artifacts at each phase.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Sequential phases (requirements→design→implementation)
Why it's wrong here
Sequential requirements-to-design-to-implementation phases describe waterfall's linear lifecycle, where each stage completes before the next begins. That model is genuinely appropriate for stable, well-understood requirements with heavy compliance gates. Agile instead delivers working increments iteratively, revisiting requirements, design and code each sprint.
- ✓
Iterative development with short cycles
Why this is correct
Iterative development with short cycles is a defining agile characteristic, delivering working software in frequent increments rather than one big-bang release. These short iterations enable continuous feedback, letting teams adapt to changing requirements throughout the project, which directly satisfies the agile emphasis on responding to change over following a rigid plan.
- ✓
Responding to change over following a plan
Why this is correct
Agile methodologies explicitly value responding to change over following a plan, as stated in the Agile Manifesto. This satisfies the question's requirement for a common agile characteristic, contrasting with plan-driven waterfall approaches that resist late requirement changes.
- ✗
Fixed scope defined at the start
Why it's wrong here
Agile deliberately welcomes changing requirements throughout delivery, so scope is continuously reprioritised rather than frozen. Fixed upfront scope is genuinely appropriate for plan-driven waterfall contracts with firm regulatory or contractual baselines. Agile instead fixes time and cost per iteration while allowing scope to flex.
- ✗
Comprehensive documentation at each phase
Why it's wrong here
Agile values working software over comprehensive documentation, producing documentation only where it adds value rather than at every phase. Phase-gated documentation is genuinely appropriate for safety-critical or audited waterfall projects. Agile instead favours lightweight artefacts, continuous feedback and just-enough up-front specification.
Go deeper
Related to this question
About these practice questions
Courseiva writes every FC0-U71 question from scratch — 988 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 →
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 FC0-U71 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 FC0-U71 exam.