Extreme Programming

Correct Answer: Integrate pair programming to facilitate better understanding and acceptance of continuous changes.

The correct approach in a scenario where team members are uncomfortable with continuous changes in Extreme Programming (XP) is to facilitate methods that help team members understand and embrace these changes. Pair programming, one of the core practices of XP, not only improves the quality of code but also helps team members to adapt to changes more readily by working closely together. The wrong answers are plausible yet incorrect approaches: adopting a hybrid approach with Waterfall contradicts the principles of XP, which embraces change; increasing iteration duration goes against the XP principle of quick feedback loops; and while empowering the team is important, allowing them to selectively implement XP practices can dilute the effectiveness of the XP methodology and does not directly address their discomfort with continuous changes.

Correct Answer: Through continuous design improvements via refactoring.

Correct Answer: Facilitate a session to emphasize the importance of pair switching for enhancing learning and improving code quality, and encourage more frequent integration.

In the context of XP (Extreme Programming) and Scrum, it's essential to encourage best practices that promote team learning, code quality, and timely integration. Pair programming is a core practice in XP designed to ensure continuous code review, knowledge sharing, and reduction of knowledge silos. Frequent switching of pairs further enhances these benefits by spreading skills and insights throughout the team. Therefore, facilitating a session to emphasize the value of these practices and encourage their adoption is the correct approach. The wrong answers, although related to team dynamics and code quality, either divert from the core XP practices without just cause or misunderstand the primary objectives of these practices in a Scrum/XP environment.