An empirical study of the impact of user involvement on system usage and information satisfaction
Communications of the ACM - The MIT Press scientific computation series
Development of computer-based information systems: A communication framework
ACM SIGMIS Database
An experimental study of fault detection in user requirements documents
ACM Transactions on Software Engineering and Methodology (TOSEM)
Innovative teaching materials and methods for systems analysis and design
ACM SIGMIS Database
Explaining the role of user participation in information system use
Management Science
“Requirements-uncertainty”: is it best formulated as a latent, aggregate or profile construct?
European Journal of Information Systems
Investigating information systems with action research
Communications of the AIS
Rapid Development: Taming Wild Software Schedules
Rapid Development: Taming Wild Software Schedules
Improving information requirements determination: a cognitive perspective
Information and Management
Information Technology Control and Audit, Second Edition
Information Technology Control and Audit, Second Edition
The ethnographically informed participatory design of a PD application to support communication
Assets '04 Proceedings of the 6th international ACM SIGACCESS conference on Computers and accessibility
A Unified Model of Requirements Elicitation
Journal of Management Information Systems
A New Standard for Quality Requirements
IEEE Software
Results from deploying a participation incentive mechanism within the enterprise
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The impacts of user review on software responsiveness: Moderating requirements uncertainty
Information and Management
A product management challenge: Creating software product value through requirements selection
Journal of Systems Architecture: the EUROMICRO Journal
Proceedings of the 2009 ACM symposium on Applied Computing
Introduction to designing information and organizations with a positive lens
Information and Organization
Practical challenges of requirements prioritization based on risk estimation
Empirical Software Engineering
Hi-index | 0.00 |
For decades and still today, software development projects have failed because they do not meet the needs of users, are over-budget, and abandoned. To help address this problem, the user requirements elicitation process was modified based on principles of Appreciative Inquiry. Appreciative Inquiry, commonly used in organizational development, aims to build organizations, processes, or systems based on success stories using a hopeful vision for an ideal future. In four studies, Appreciative Inquiry was evaluated for its effectiveness with eliciting user requirements in different circumstances. In the first two studies, it was compared with brainstorming, a traditional approach, with end-users (study 1) and proxy-users (study 2). The third study was a quasi-experiment comparing the use of Appreciative Inquiry in different phases in the software development cycle (study 3). The final (fourth) study combined all lessons learned using Appreciative Inquiry in a cross-case comparison study of 3 cases to gain additional understanding of the requirements gathered during various project phases. In each of the four studies, the requirements gathered, developer and user attitudes, and the Appreciative Inquiry process itself were evaluated. Requirements were evaluated for their quantity and type regardless of whether they were implemented or not. Attitudes were evaluated for commitment to the requirements and project using process feedback. The Appreciative Inquiry process was evaluated with differing groups, projects, and project phases to determine how and when it is best applied. Potentially interceding factors were also evaluated including: team effectiveness, Emotional Intelligence, and perceived stress. Appreciative Inquiry produced positive results for the participants, the requirements obtained, and the general requirements eliciting-process. Appreciative Inquiry demonstrated benefits to the requirements gathered by increasing the number of unique requirements as well as identifying more quality-based (non-functional) and forward-looking requirements. It worked best when there was time for participants to reflect on the thought-provoking questions and when the facilitator was knowledgeable of the subject-matter and had extra time to extract and translate the requirements. The participants (end-users and developers) expressed improved project understanding. End-users participated consistently with immediate buy-in and enthusiasm, especially those users who were technically-inhibited. We conclude that Appreciative Inquiry can augment existing methods by presenting a positive and future aspect for a proposed system resulting in improved user requirements.