{'fraction_non_alphanumeric': 0.01805869074492099, 'fraction_numerical': 0.0, 'mean_word_length': 5.619402985074627, '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}}
Empirical validation of pair programming

This paper discusses an empirical assessment of pair programming. Several agile processes arose and have been adopted in industry with the promise of producing working software in the early phases of production process and to make the organization flexible and adaptable with respect to the changing environment. The outcomes of the experiments can be summarized as follows: (i) pair programming improves the productivity of developers with respect to solo programming; (ii) it also fosters knowledge transfer between the developers of the pair: the experiment suggests that this effect is emphasized when both the components own the same educational background; and, finally, (iii) distributing the components of a pair could seriously deteriorate expected benefits, if an appropriate support for communication and collaboration is not set up.