{'fraction_non_alphanumeric': 0.016036655211912942, 'fraction_numerical': 0.0, 'mean_word_length': 5.198581560283688, '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}}
PD method and socio-political context of the development organization

Little research is done on how socio-political factors intertwine with method implementation. This paper is a follow up of a reported PD method implementation failure four years ago. For branch related reasons, the implementation fell short. This article tells the story of what happened then. To our surprise, the original reason for introducing the PD method called Personas had disappeared during our one and a half year attempt at method implementation. Internal socio-political developments had solved the power struggle that the PD method was aimed to mediate. We propose that it is time to expand the method focus with studies revealing more about the socio-political internal climate and contingencies in today's software development practices that influence method introduction and adaptation.