Investigating the State of User Involvement in Practice

Heiskari, Juho; Lehtola, Laura

doi:10.1109/apsec.2009.64

Cited by 12 publications

(7 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Other studies (e.g. [7], [9], [18]) support our findings, what makes us confident that the identified problems are real. Ensuring construct validity for empirical studies of software developers is always a complex task, specifically as such studies typically require the researcher to abstract from observed behavior or gathered information.…”

Section: B Limitationssupporting

confidence: 89%

“…Heiskari and Lehtola [7] investigate user involvement in practice without focusing on a specific development lifecycle phase, and identify several challenges which are confirmed by our study. First, similarly to our results the authors found that user information is scattered, unorganized, and difficult to access (Hypothesis 1), and that there is no clear and common process on understanding users (Hypothesis 4).…”

Section: Related Worksupporting

confidence: 57%

See 1 more Smart Citation

User involvement in software evolution practice: A case study

Pagano

Bruegge

2013

2013 35th International Conference on Software Engineering (ICSE)

View full text Add to dashboard Cite

User involvement in software engineering has been researched over the last three decades. However, existing studies concentrate mainly on early phases of user-centered design projects, while little is known about how professionals work with post-deployment end-user feedback. In this paper we report on an empirical case study that explores the current practice of user involvement during software evolution.We found that user feedback contains important information for developers, helps to improve software quality and to identify missing features. In order to assess its relevance and potential impact, developers need to analyze the gathered feedback, which is mostly accomplished manually and consequently requires high effort. Overall, our results show the need for tool support to consolidate, structure, analyze, and track user feedback, particularly when feedback volume is high. Our findings call for a hypothesis-driven analysis of user feedback to establish the foundations for future user feedback tools.

show abstract

Section: B Limitationssupporting

confidence: 89%

Section: Related Worksupporting

confidence: 57%

User involvement in software evolution practice: A case study

Pagano

Bruegge

2013

2013 35th International Conference on Software Engineering (ICSE)

View full text Add to dashboard Cite

show abstract

“…According to Bano and Zowghi (2015), "the most prominent problems caused by user involvement are communication problems and misunderstandings between the users and the development teams leading to all kinds of conflicts." Conflicts always make their way between the team and users, therefore the management must adopt conflict management strategies to handle them effectively (Heiskari and Lehtola, 2009). Melo (2013) found that problems are caused by not being "able to manage the conflicts regarding the work procedures, leading to turnover and decreased productivity in the short term (teams were unable to deliver for a while), as well as loss in both knowledge and team overhead after the turnover."…”

Section: Relationship Conflicts "Involve Disagreements Amongmentioning

confidence: 99%

Grounded Theory Study of Conflicts in Norwegian Agile Software Projects: The Project Managers’ Perspective

Siddique¹,

Hussein²

2016

EPPM-Journal

View full text Add to dashboard Cite

This paper aims to explore the process of conflicts in agile software projects. The purpose was to investigate the causes and consequences of these conflicts. For this purpose, we conducted a qualitative study involving agile software projects in Norway. Grounded theory was used to analyze the data and the interview findings are presented using Glaser´s Six C model (context, condition, causes, consequences, contingencies, and covariance). The research findings suggest that there are several causes of conflicts. These include: the role of the product owner, an inexperienced project manager, the customer's lack of knowledge about methodology organizational hierarchy in public companies, contracting, personal egos, financial issues, not getting the right team. Consequences of conflicts include: decreased productivity, wastage of time and resources, diverted attention from project objectives loss of motivation, poor decision making, loss of communication. Based on interview data, different conflict strategies are suggested and these include appropriately skilled project manager, communication and negotiation, defining clear roles, stakeholder analysis, managing stakeholder´s expectations, discussion, finding the root cause of conflict. Project managers are using these strategies to avoid or resolve conflicts. The competencies required to handle these kind of conflicts are also discussed in the paper, while the implications of theory and practice of conflict management theory are also presented.

show abstract

“…The development of novel software products, as well as the improvement of existing ones, can deeply benefit from the involvement of users in requirements engineering (RE) activities (Bano and Zowghi, 2015). Getting feedback from the user base has been recognised to lead to increased usability, improved satisfaction (Bakalova and Daneva, 2011), better understanding of requirements (Hanssen and Faegri, 2006), and creation of long-term relationships with customers (Heiskari and Lehtola, 2009). User feedback can take implicit and explicit forms, and different means are available to collect this information.…”

Section: Introductionmentioning

confidence: 99%

Using Voice and Biofeedback to Predict User Engagement during Requirements Interviews

Ferrari¹,

Huichapa²,

Spoletini³

et al. 2021

Preprint

View full text Add to dashboard Cite

Capturing users’ engagement is crucial for gathering feedback about the features of a software product. In a market-driven context, current approaches to collect and analyze users’ feedback are based on techniques leveraging information extracted from product reviews and social media. These approaches are hardly applicable in bespoke software development, or in contexts in which one needs to gather information from specific users. In such cases, companies need to resort to face-to-face interviews to get feedback on their products. In this paper, we propose to utilize biometric data, in terms of physiological and voice features, to complement interviews with information about the engagement of the user on the discussed product-relevant topics. We evaluate our approach by interviewing users while gathering their physiological data (i.e., biofeedback) using an Empatica E4 wristband, and capturing their voice through the default audio-recorder of a common laptop. Our results show that we can predict users' engagement by training supervised machine learning algorithms on biometric data, and that voice features alone can be sufficiently effective. The performance of the prediction algorithms are maximised when pre-processing the training data with the synthetic minority oversampling technique (SMOTE). The results of our work suggest that biofeedback and voice analysis can be used to facilitate prioritization of requirements oriented to product improvement, and to steer the interview based on users' engagement. Furthermore, the usage of voice features can be particularly helpful for emotion-aware requirements elicitation in remote communication, either performed by human analysts or voice-based chatbots.

show abstract

Investigating the State of User Involvement in Practice

Cited by 12 publications

References 19 publications

User involvement in software evolution practice: A case study

User involvement in software evolution practice: A case study

Grounded Theory Study of Conflicts in Norwegian Agile Software Projects: The Project Managers’ Perspective

Using Voice and Biofeedback to Predict User Engagement during Requirements Interviews

Contact Info

Product

Resources

About