{'fraction_non_alphanumeric': 0.01348747591522158, 'fraction_numerical': 0.005780346820809248, 'mean_word_length': 5.046511627906977, '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}}
Agile with Fragile Large Legacy Applications

Can you imagine applying agility to a huge legacy code base over a decade old, supported by a 100+ person distributed development team? Agitar works with customers who have this type of fragile legacy code environment. These customers seek to improve code quality and reduce risk by formalizing a unit test discipline without disrupting the business. In this paper, we share our experience of how three teams with large legacy applications moved from fragile towards agile.