Pair Programming - Myth Busters!
“If a task takes 1 hour; it takes 2 hours in pair programming.”
“This fix is needed urgently; it is better done alone to save time.”
“It is good only for complicated tasks; there is no need to pair program on simple tasks.”
These are some of the statements you may be hearing around you from experienced developers to even managers. Sadly, there is lack of understanding of dynamics that make pair programming a key agile engineering practice. This, in turn, resulted in lack of its acceptance in teams adopting agile methodologies. Our mission is to dissect the myths around pair programming which brings continuous learning, productivity, quality, and the joy of collaboration to countless developers every day.