Test your Pair Programming knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What are the "driver" and "navigator" roles in the classic pair programming model, and how do they typically differ?
Questions in this quiz
What are the "driver" and "navigator" roles in the classic pair programming model, and how do they typically differ?
What is a reasonable perspective on how pair programming can affect a team's "bus factor" (the risk of a project stalling if a specific key person becomes unavailable)?
What is a reasonable perspective on whether pair programming should be MANDATORY for all work on a team, versus an optional tool used situationally?
What is "driver-navigator switching," and why is it generally recommended to switch roles periodically during a pairing session?
What is a reasonable justification for using pair programming specifically when onboarding a new hire during their first days/weeks at a company, beyond general knowledge transfer?
What is a reasonable approach to deciding WHEN pair programming is most worth using, given its real resource cost, versus when solo development is likely more appropriate?
What is a commonly cited knowledge-sharing benefit of pair programming, particularly relevant for onboarding a new team member or spreading expertise across a team?
What is a reasonable way pair programming can affect code review practices, given that a pair has already had two sets of eyes on the code during its actual creation?
What is a reasonable way to think about the relationship between pair programming and code ownership within a team -- does pairing tend to encourage more individual or more collective ownership of code?
What is a commonly cited drawback or cost of pair programming, compared to two developers each working independently on separate tasks?
What is "mob programming" (or "ensemble programming"), and how does it relate to (but differ from) traditional two-person pair programming?
What is a reasonable concern about personality/working-style mismatches affecting the effectiveness of a specific pair programming partnership?