{'fraction_non_alphanumeric': 0.018518518518518517, 'fraction_numerical': 0.0013227513227513227, 'mean_word_length': 5.007936507936508, '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}}
The pairing session as the atomic unit of work

We have an extreme programming team at a small company dedicated to the agile approach. Our team of 7 developers decided to use the pairing session as the fundamental unit of work for all organizing, planning, estimating, tracking, and of course, pair programming. It's been a great way to structure the day, provide rhythm and facilitate partner swaps. Estimating and tracking in pairing sessions provides us concrete feedback for improving estimates. This approach constitutes a hybrid between real time and abstract-unit estimating, resulting in highly effective planning and an extremely stable velocity. We have been working this way for about a year and have been exceptionally pleased with the results