Pair programming is a proven agile technique for improving quality, sharing knowledge, and ramping up less experienced developers. The PMI Agile Practice Guide (Section 5.5: Quality and Engineering Practices) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance) recommend using pair programming to improve team cohesion and performance when skill gaps are affecting velocity.
Option A is correct: pair programming supports learning and improves delivery quality.
Option B misuses the retrospective—it’s not for backlog prioritization.
Option C may be helpful, but estimation changes don’t directly address the skill gap.
Option D may reduce risk short-term but doesn’t help the team improve or grow.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit