{'fraction_non_alphanumeric': 0.017204301075268817, 'fraction_numerical': 0.0, 'mean_word_length': 5.553990610328638, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Case study: Factors that hinder and support the adoption of Pair Programming in an agile software development company

Pair programming is the XP practice that is the least adopted in software development departments or companies; although previous research suggests there are numerous benefits that can be realised from its use. It is suggested that this practice, which involves two programmers working collaboratively on the same task and following a prescribed approach, produces high quality code, in shorter timeframes, with increased knowledge-sharing and improved developer productivity. This paper investigates the factors that support, and deter, pair programming adoption in a case study at a software development company in the eThekwini (Durban) region, South Africa. The survey and interviews indicate that the most positive influences are the support from senior and peer staff and the company's willingness to provide the necessary hardware, software and physical layout to enable the use of pair programming. The biggest challenge was the personality mix in a pair, for example introvert/extrovert pairs, where extroverts can dominate pair collaboration. This company has specific managerial guidelines and practices which are used to mitigate the challenges and provide support to, not only make pair programming a more operationally feasible option, but also reap its benefits