{'fraction_non_alphanumeric': 0.014787430683918669, 'fraction_numerical': 0.0, 'mean_word_length': 5.050279329608938, '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}}
Is Extreme Programming Just Old Wine in New Bottles: A Comparison of Two Cases

This article explores extreme programming (XP) as an information systems development approach and argues that it is mainly old wine in new bottles. We take an interpretive and critical view of the phenomenon. We made an empirical study of two companies that apply an XP-style development approach throughout the information systems development life cycle. The results of our research suggest that XP is a combination of best practices of traditional information systems development methods. It is hindered by its reliance on talented individuals, which makes its large-scale deployment as a general-purpose method difficult. We claim that XP can be useful for small teams of domain experts who are physically close together and able to communicate well with the end users, and who are good designers and implementers. However, these skilled and motivated individuals with high working moral can exhibit high productivity regardless of the methods used if they are not overly constrained by bureaucracy.