{'fraction_non_alphanumeric': 0.01861427094105481, 'fraction_numerical': 0.0, 'mean_word_length': 5.245161290322581, '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}}
The development is driven by our users not by ourselves-including users in the development of off-the-shelf software

This article describes a non-traditional approach to Participatory Design where distributed users have a serious impact on a software development process. The small software provider makes use of a non-traditional way of Participatory Design combined with an agile development approach. By using for among other things support service, user meetings, courses and news letter they are able to on a daily bases keep in contact with users. Users convey requirements for new functionalities, give feedback and report errors. Users’ feedback and proposals form the base for further development. Frequent re-leases allow the company to quickly implement improvements and bug-fixes. The article relates the observed practices to other research on Participatory Design in unconventional settings and discusses how to expand the Participatory Design toolbox.