{'fraction_non_alphanumeric': 0.020603384841795438, 'fraction_numerical': 0.004415011037527594, 'mean_word_length': 5.044444444444444, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Fuzzy Artefacts: Formality of Communication in Agile Teams

Agile Software Development (ASD) is often thought of as to predominantly use face-to-face communication. Research over the last years already led to adjustment of this conception. ASD also uses formal communication where it blends both traditional and agile artefacts. A next step should then be to explore the entire spectrum from informal to formal communication. This raised our research question: Which artefacts do agile teams use in between formal communication with artefacts and informal face-to-face communication? In an exploratory multiple single-case study we found 38 agile teams in as many organizations willing to participate in answering our question. The findings from our case study confirm the existence of what we called fuzzy artefacts, concepts which are not formally documented but are of such a pervasive nature that an agile team is well aware of their existence. We found in total 73 individual fuzzy artefacts in 38 agile teams. Most of them are related to requirements. Populating a product or sprint backlog with user stories equipped with priorities and efforts is another area where they were found. In this way we extended the typology of formal communication (artefacts) and informal communication (face-to-face) in ASD with an intermediate concept: fuzzy artefacts.