What are three practices of Extreme Programming (XP)? (Choose three.)You have reached the max number of allowed answers

Question

Options

• ABehavior-driven development
• BIntentional architecture
• CTest-driven development
• DDeployment automation
• EPair programming
• FContinuous Integration

• A
  4% (1)
• C
  93% (25)
• D
  4% (1)

Explanation

Test-Driven Development (C), Pair Programming (E), and Continuous Integration (F) are three of XP's foundational practices, codified by Kent Beck. TDD means writing automated tests before writing code, forcing small feedback loops. Pair Programming places two developers at one keyboard, improving code quality through constant review. Continuous Integration requires developers to merge and build code frequently (often multiple times per day), catching integration issues early.

Why the distractors are wrong:

• A (BDD): Behavior-Driven Development evolved from TDD (popularized by Dan North) but is a distinct practice not part of XP's core set.
• B (Intentional Architecture): This is a SAFe (Scaled Agile Framework) concept - planned, deliberate system design at scale - not XP.
• D (Deployment Automation): A DevOps/CD pipeline practice; XP focuses on integration, not automated deployment.

Memory tip: Think of XP as "doing good things to the extreme" - write tests first (TDD), never code alone (Pair Programming), and integrate constantly (CI). If a choice sounds more like DevOps or SAFe, it's almost certainly not XP.

No community discussion yet for this question.