Blog post series
This blog post is part of a series about pair-programming games. To read about more please click see more sessions on pair-programming games.
- You have very stubborn programmers in your team and you want to make his views softer.
- To any problem, your team says there is only one solution, and that is their solution. You want to let them see there are always alternate solutions, which sometimes are better.
- You had issues in the past with architectural or design decisions, just because the problem was not understood sufficiently.
A very experienced and neutral person, ideally an external technical coach, will pair with the team members one by one.
The rules are that:
- the team member will be the driver
- the technical coach will be the navigator
- the technical coach is allowed to always ask beginner, even basic and stupid questions like “what are you doing”, “why are you doing this”, “tell me what is happening in this code”
- the driver is not allowed to be angry by the beginner questions of the technical coach; the driver needs to always explain what is their current idea, how they can implement it and why they chose this path.
These sessions should have a specific, very clear topic. The technical coach needs to make sure that each member of the team understood the purpose.
The pair-programming session should not last more than 30-60 minutes as it is very tiring for both of the performers.