Which Agile Methodology Best Fits a Two-Developer Team with Changing Requirements?

A project coordinator has started a new project and is reviewing the following characteristics provided by the customer: • Two developers • High uncertainty about existing systems • Risk of frequent requirement changes • Tight deadlines Which of the following project methodologies would be BEST to use in this situation?

  1. PRINCE2
  2. Scrum
  3. SAFe
  4. XP Source Reference Answer

Community Votes

D
62%
B
38%

62% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

Tests recognition of methodology-specific technical practices, with the common trap being the automatic selection of Scrum as the default Agile choice despite the critical two-developer constraint.

This question evaluates understanding of Agile frameworks, specifically matching project constraints to the appropriate methodology. Community consensus strongly favors Extreme Programming (XP) due to its engineering-focused practices tailored for small teams and volatile requirements.

Scrum (Option B) is the most frequent incorrect choice because candidates overlook XP’s mandatory pair programming practice, which directly addresses the two-developer setup and high technical uncertainty.

Community Discussion (5 comments)

95d3b92 👍 1 Selected: D
My initial thought was Scrum, but the key here is the size of the team. Since the team is small, XP makes the most sense in this scenario.
044f354 👍 2 Selected: D
This one is easy folks... • Two developers = pair programming • High uncertainty about existing systems = high amount of risk associated with the project • Risk of frequent requirement changes = dynamically changing user requirements • Tight deadlines = delivering the software that's needed when the customer needs it from CompTIA Project+ Study Guide, 3rd Edition Chapter 4: Planning the Project "XP involves delivering the software that's needed when the customer needs it. Consider using XP under these conditions: When there are dynamically changing user requirements. This typically happens when the customer, or end user, doesn't have a clear idea of what they need. When a high amount of risk is associated with the project. When you have small development teams of between two and 12 programmers. ... There are always two developers working in pairs at the same computer."
xplicit670 👍 1 Selected: B
Scrum is best for small developers. XP is with larger teams
ID77 👍 2 Selected: B
Scrum is an Agile methodology that works well in environments with high uncertainty, changing requirements, and tight deadlines. While XP is a good fit for projects requiring high-quality code and frequent iteration, Scrum is a more comprehensive framework for managing the entire project, especially with a small team and tight deadlines.
107b145 👍 2 Selected: D
XP (Extreme Programming): XP is an Agile methodology designed to improve software quality and responsiveness to changing customer requirements. It focuses on frequent releases in short development cycles, which improves productivity and introduces checkpoints at which new customer requirements can be adopted. XP emphasizes close collaboration between developers and customers, continuous testing, and rapid feedback, making it well-suited for situations with high uncertainty and frequent requirement changes.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Extreme Programming (XP) is explicitly engineered for small teams navigating high uncertainty and frequent requirement shifts. Its foundational practice of pair programming perfectly aligns with the two-developer constraint, ensuring immediate peer review, knowledge transfer, and higher code quality. Furthermore, XP’s short iteration cycles and continuous integration enable rapid delivery under tight deadlines.

Why the Other Options Are Wrong

PRINCE2 (A) relies on structured phases and heavy documentation, making it ill-suited for high volatility and rapid adaptation. Scrum (B) provides strong project management scaffolding but deliberately omits specific software engineering practices, leaving technical risk unaddressed. SAFe (C) is an enterprise-level scaling framework designed for dozens of coordinated teams, rendering it entirely impractical for a two-person project.

Community Comment Notes

Multiple contributors correctly linked the "two developers" clue to XP’s signature pair programming practice [1][4]. One user initially gravitated toward Scrum but pivoted after recognizing that XP better handles the technical uncertainty and small team dynamics [4]. Another highlighted XP’s focus on frequent releases and adaptive requirements, validating its fit for tight schedules [3]. While Scrum debates are common, the explicit team size remains the definitive differentiator.

Official Reference

Exam Strategy

When encountering Agile methodology questions, prioritize team size and technical constraints over general familiarity. Keywords like "pair programming," "test-driven development," or specific headcounts often signal XP, whereas roles like "Product Owner" or "Sprint Master" point to Scrum.

Related Analysis

Someone claiming to be from a tax agency sent an email to a

S-Grade

Which of the following can a project manager infer from the

S-Grade

A company needs to have structured cabling installed in one

A-Grade

Practice All PK0-005 Questions

Access 102 questions with complete answers and detailed explanations.

View Full PK0-005 Practice Test →

← Back to PK0-005 Study Guide