CAPM Agile Frameworks and Methodologies Practice Question
A geographically distributed agile team using Scrum is experiencing frequent integration issues and delays caused by incompatible code changes. Which Extreme Programming (XP) practice would best address this problem?
⚠ Common exam trap
CAPM often tests the distinction between XP practices, and candidates may confuse continuous integration with test-driven development or pair programming, overlooking that CI specifically targets integration frequency and automation.
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
✓
Continuous integration
Continuous integration (CI) is an XP practice where team members integrate their code changes into a shared repository multiple times a day, with each integration verified by an automated build and test suite. For a geographically distributed Scrum team, CI directly addresses integration issues by catching incompatible changes early, reducing the time and effort required to resolve conflicts. It ensures that code from different developers is continuously merged and validated, preventing the accumulation of divergent changes that cause delays.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Pair programming
Why it's wrong here
Pair programming puts two developers at one workstation, which distributed teams cannot do synchronously across time zones, and it does not merge divergent branches. It is tempting because it spreads code ownership and catches defects early, but continuous integration is the practice that performs frequent automated merges to surface incompatible changes.
- ✓
Continuous integration
Why this is correct
Continuous integration requires developers to merge code into a shared repository frequently, with automated builds and tests detecting incompatibilities early. This directly resolves the distributed team's integration issues and delays caused by incompatible code changes, a specific XP practice addressing exactly that constraint.
- ✗
Test-driven development (TDD)
Why it's wrong here
TDD ensures unit tests are written first, but it does not by itself prevent integration problems.
- ✗
Refactoring
Why it's wrong here
Refactoring restructures code without changing behaviour, so it cannot prevent incompatible changes reaching integration. It tempts as a code-quality practice, but continuous integration, with frequent automated builds and tests, is the XP practice that catches integration conflicts early.
Visual reference
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-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 PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI 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 CAPM exam.