{'fraction_non_alphanumeric': 0.02192638997650744, 'fraction_numerical': 0.0, 'mean_word_length': 5.761904761904762, '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}}
Extending socio-technical congruence with awareness relationships

Coordination in software engineering is necessary for software teams. To study coordination, researchers need a a way to conceptualize and measure it|one such measure is socio-technical congruence. Within a team setting, awareness of other's tasks and abilities enables coordination, but the conceptualizations for socio-technical congruence do not include awareness. In this paper, our goal is to include awareness in socio-technical congruence. To do this, we conduct an empirical investigation of a team's awareness behaviour. We examine how developers transmit awareness information in a global software-engineering environment in a project called Ship using direct observations, interviews, and a questionnaire. We found that team members were satisfied with using simple awareness mechanisms such as email and meetings. We also identified that experienced team members served as brokers and filled coordination gaps, and that team members used multiple types of media simultaneously. Based on this work, we propose an aggregated sociotechnical congruence measurement that can be used to specify multiple relationships, such as awareness relationships, as interactions that satisfy technical dependencies.