A municipal benefits-calculator team comparing Extreme Programming (XP) with Scrum notices developers freely improve any module. Which XP practice does that reflect that Scrum does not prescribe as a core component?
Select an answer to reveal the explanation.
Short Explanation
XP treats the codebase like a shared kitchen—anyone can tidy a messy drawer. Collective code ownership (often with pairing) is an XP engineering habit Scrum never hard-wires. Scrum stays quiet on who owns which files; XP leans into shared craft.
Full Explanation
Extreme Programming emphasizes engineering practices such as collective code ownership and pair programming. Scrum defines accountabilities, events, and artifacts but does not prescribe collective ownership or pairing as required components. Recognizing that difference helps teams pick practices intentionally rather than assuming every agile label includes the same engineering toolkit.