Exam PK0-005 topic 1 question 195 discussion

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.

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."

Scrum is best for small developers. XP is with larger teams

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.

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.