Power and politics of user involvement in software development

© 2018 Association for Computing Machinery. [CONTEXT] Involving users in software development is a complex and multi-faceted concept. Empirical research that studies power and politics of user involvement in software development is scarce. [OBJECTIVE] In this paper, we present the results from a case study of a software development project, where organizational politics was explored in context of user involvement in software development. [METHOD] We collected data through 30 interviews with 20 participants, attending workshops, observing project meetings, and analysing projects documents. The qualitative data was rigorously and iteratively analyzed. [RESULTS] The results indicate that the politics was a significant factor used to exert power and influence in decision-making processes. Communication channels were exploited for political purposes. These contributed to the users' dissatisfaction with their involvement thus impacting on the project outcome. [CONCLUSION] Having multiple teams of stakeholders with different levels of power in decision-making, the politics is inevitable and inescapable. Without careful attention, the political aspect of user involvement in software development can contribute to unsuccessful project

Modelling the Political Context in Software Requirements Engineering

The influence of stakeholder politics on the outcome of software development projects has been identified as a major issue in the practice of software Requirements Engineering (RE) that has been left substantially overlooked in the field and practice of RE. I argue that politics and power are crucial aspects not just influencing RE but being part of it and integral components of the process. A practical solution in the form of a notation that will aid practitioners both to identify explicit and implicit stakeholders and to document the current state of their degree of support for that project is proposed. An Emoji pictograms-based notation called Political Emoji Notation (PEN) was created which is based on an existing well-known visual language, easily adoptable by requirements engineers. RE professionals will be able to identify and document power, politics and the emotional aspects that come into play during software requirements-related decision-making. PEN is intended solely for the use of RE and their team, ensuring complete confidentiality and avoiding any political engagement with the customer. The notation is deliberately kept simple, to minimise the learning process and enable practical use without the need for specialised software for drawing diagrams, and is readily accessible and user-friendly. The notation underwent testing using two case studies of unsuccessful software projects well documented in the literature. From the analysis of the two case studies, a set of symptoms has been identified to identify projects that are at risk. Finally, the thesis proposes potential directions for future research and work based on the implementation of this notation