User satisfaction and system success: an empirical exploration of user involvement in software development

Bano, Muneera; Zowghi, Didar; Rimini, Francesca da

doi:10.1007/s10664-016-9465-1

Cited by 49 publications

(31 citation statements)

References 61 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…To answer our research question, the analysis of case study data revealed that intra-organizational politics resulted in dissatisfaction of users about their involvement in the SDP. In previous studies [25], the satisfaction of users with the process of their involvement has been observed to be mutually constituted with their satisfaction with the product (system). In our case study, we observed the similar phenomenon; the users were dissatisfied with their involvement and this contributed to their dissatisfaction about the project outcome (product/system).…”

Section: Resultsmentioning

confidence: 96%

See 1 more Smart Citation

Power and Politics of User Involvement in Software Development

Bano

Zowghi

Rimini

2018

Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Section: Resultsmentioning

confidence: 96%

“…Defining the term 'user' is contextual for any specific software project [25], however, a user is typically considered to be someone who would be actually using the system and can play various roles on different levels in an organization or a team [1].…”

Section: Introductionmentioning

confidence: 99%

Power and Politics of User Involvement in Software Development

Bano

Zowghi

Rimini

2018

Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018

Self Cite

View full text Add to dashboard Cite

show abstract

“…On a larger extent, user's involvement was linked with quality. Bano and Zowghi [9] explain that applying and utilizing the collaborative approach helps to bring unity among different users, which leads to the sharing of ideas leading to continuous growth. The method the authors proposed was linking user's involvement with success, and how it makes the user satisfaction and acceptance possible and reachable.…”

Section: Litrature Reviewmentioning

confidence: 99%

The impact of user involvement in software development process

saif

Almohawes

Jamail

2021

IJEECS

View full text Add to dashboard Cite

<p>In software development process, user can take part in any phase of the process, depending on what model is being applied. Lack of user involvement can result in a poorly designed solution, or even a solution that conflicts with user’s needs. This review paper presents the impact of user involvement in software development process. In this study, different software development processes will be reviewed, show where the user usually gets involved in different models such as: Structural (Waterfall, V-model) and incremental (Scrum-extreme programming XP). As each model differs from the other, each of them has a different perspective of where user should take part and where they should not. This can be an asset that helps project managers, and leaders to develop suitable strategies to follow in their projects.</p>

show abstract

“…Generally, during the interview or requirement gathering process, some of the important steps which an interviewer usually takes care of are: (i) preparation, (ii) execution of the interview, and (iii) developing chemistry and conversation with the interviewee [42][43][44]. In our proposed method, our main focus is on 'involving stakeholders (enhancing conversation and openness between stakeholders)', and we believe that this goal can be achieved by multiple ways, two of which we propose are: (i) extracting information using story-phases-based activity or story building/completing; (ii) three thinking lens activity for eliciting requirements adapted from [45].…”

Section: Story-based Approach For Requirements Elicitationmentioning

confidence: 99%

“…One of the most important factors is the client/user involvement. User involvement can be gauged and explained by the: (i) degree and level of user involvement; (ii) techniques and methods of user involvement [42, 43]. Some of the essential things in requirements gathering session are knowing what to ask, how to ask, and why to ask that aspect in particular?…”

Section: Social Engineers As Requirements Elicitor and Story Tellermentioning

confidence: 99%

Improving software requirements reasoning by novices: a story‐based approach

et al. 2019

View full text Add to dashboard Cite

Requirements elicitation is one of the essential steps towards software design and construction. Business analysts and stakeholders often face challenges in gathering or conveying key software requirements. There are many methods and tools designed by researchers and practitioners but with the persistent development of new technologies, there is a need to make requirements gathering and design-rationale process more efficient and adaptable. Storytelling is an emerging concept and researchers are witnessing its effectiveness in education, community building, information system, and requirement elicitation. Objectives of this study are to devise a method for requirements elicitation and improving design-rationales using story-based techniques and evaluate the effectiveness of the proposed activity. To answer the research objectives, the authors have conducted open-ended interviews to get feedback on the proposed method; the authors have case requirement from a running project to map how this method can be useful; and performed empirical evaluation of the proposed card-based activity. The estimated regression model, in our study, has shown that participants' perception about the simplicity/easiness and the joy of playing the game has an eventual positive effect on requirements elicitation through enhancing user's desire to play the game, which in turn increases the collaborative learning outcomes of the game.

show abstract

User satisfaction and system success: an empirical exploration of user involvement in software development

Cited by 49 publications

References 61 publications

Power and Politics of User Involvement in Software Development

Power and Politics of User Involvement in Software Development

The impact of user involvement in software development process

Improving software requirements reasoning by novices: a story‐based approach

Contact Info

Product

Resources

About