Possible Root Causes of Pair Programming Adoption Failure

While working with teams, often found team members are waiting to get their code reviewed and that surprise me, why don’t they adopt pair programming in their team culture to get away additional software waste from their software lead time to deliver requirements.

More often you would find some of the team behaviors which prevent to have successful a pairing strategy in your team

My Way or No Way

Individuals with good experience in domain expertise often into dilemmas that whatsoever solution will always be the most suitable for the given problem. This is toxic behavior and it may harm the overall team culture

Lazy Drivers

Those who are playing the driver role in a pair programming flavor presume their job is to just help his or her partner by typing the solutions and therefore in such a situation navigator will fully implement the solution without much interference or coordination from the driver. This may become a failure of pairings in the future because one partner is completely passive without active contribution.

Disrespectful Behavior

When two persons work together, more often peers within the team together that may give a sense of competitor to each other, thus in such pairings we may find some behavior issues or need an observer to tie break to finalize the solution.

Failure is the end of the world

When pairing will be formed for the first time at a time when initially pairing with team members have initial collaboration issue, and therefore those individuals get the perception that working in pairs may not effective to deliver. ??????????

Let me do my work and you do your work

When the pair starts taking the route to work individually and complete their collaborative effort into siloed approach then pairing becomes just a name and the pairing concept itself may fail. There is a possibility when a pair is formed with junior and experienced team members.

Complete everything at one go

When pairs don’t take a break in between their pairing session and work continuously, such pairing sessions become exhaustive and pairs feel to work individually rather in pairs. This is one of a reason pairing always looks exhaustive

No Standards and Agreements

If the team doesn’t agree?and your partner starts a problem writing implementation code without any agreements, there will be a lot of communication and collaboration issues.

These are some of the issues explained leading to the collapse of the pairing culture within the team, however, there are better techniques available which I will describe in the next article.?

?

?