{'fraction_non_alphanumeric': 0.015274949083503055, 'fraction_numerical': 0.0, 'mean_word_length': 4.9939024390243905, '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}}
Configuration Management: Mother's Little Helper for Global Agile Projects?

There are many good reasons for turning co-located projects distributed, likewise there are many good reasons for turning traditional projects agile. In both cases there are many obstacles to overcome and pitfalls to avoid and the combination of agile and distributed does not make this situation any better. In general Configuration Management works as the infrastructure of any software project and its concepts and principles have to be implemented in different ways depending on the specific context. How to adapt Configuration Management for an agile context is well understood, how to adapt it for distribution is less understood -- and what changes and how to fix that when a co-located agile team goes distributed is unclear. In this position paper, we draw on our experience from academic and industrial agile projects to give our opinions on what to look out for and possibilities for solutions.