Generating user stories in groups

Authors:
Cuong D. Nguyen;Erin Gallagher;Aaron Read;Gert-Jan De Vreede
Affiliations:
Center for Collaboration Science, University of Nebraska Omaha;Center for Collaboration Science, University of Nebraska Omaha;Center for Collaboration Science, University of Nebraska Omaha;Center for Collaboration Science, University of Nebraska Omaha
Venue:
CRIWG'09 Proceedings of the 15th international conference on Groupware: design, implementation, and use
Year:
2009

Citing 11
Cited 0

Requirements engineering: a roadmap

Proceedings of the Conference on The Future of Software Engineering
Tell me a good story: using narrative analysis to examine information requirements interviews during an ERP implementation

ACM SIGMIS Database - Special issue on Critical analysis of ERP systems: the macro level
Planning Extreme Programming

Planning Extreme Programming
Extreme Programming Installed

Extreme Programming Installed
Agile Software Development: The Business of Innovation

Computer
Requirements Engineering as a Success Factor in Software Projects

IEEE Software
New directions on agile methods: a comparative analysis

Proceedings of the 25th International Conference on Software Engineering
The Cognitive Network Model of Creativity: a New Causal Model of Creativity and a New Brainstorming Technique

HICSS '00 Proceedings of the 33rd Hawaii International Conference on System Sciences-Volume 7 - Volume 7
Scenario-Based Requirements Engineering

RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
User Stories Applied: For Agile Software Development

User Stories Applied: For Agile Software Development
Integrating Collaborative Processes and Quality Assurance Techniques: Experiences from Requirements Negotiation

Journal of Management Information Systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

Communicating about system requirements with user stories is a distinctive feature of Agile Software Development methods. While user stories make system requirements intelligible to both customers and technical developers, they also create new challenges for the requirements elicitation process such as personal bias and requirements coverage. In this study we propose that when elicited from groups instead of individuals, the number of stories generated, the uniqueness and the comprehensiveness of the stories is likely to increase. A lab experiment design is delineated and partially completed. Future research will need to be conducted to determine conclusions.