What\u27s in a user story: IS development methods as communication

This paper challenges claims made by Scrum proponents when characterising the communicative nature of user stories: including being more \u27authentic\u27 because they comprise spoken language and that they are stories. We argue and decisively demonstrate that neither can be upheld. By incorrectly characterising user stories, we miss opportunities to understand what they are and how they work during development. User stories are better understood by applying a functional theory of communication that emphasises how language is used. By selecting systemic functional linguistics, we can analyse user stories, and have developed a method for factoring unwanted epics into usable user stories

What’s in a User Story: IS Development Methods as Communication

This paper challenges claims made by Scrum proponents when characterising the communicative nature of user stories: including being more ‘authentic’ because they comprise spoken language and that they are stories. We argue and decisively demonstrate that neither can be upheld. By incorrectly characterising user stories, we miss opportunities to understand what they are and how they work during development. User stories are better understood by applying a functional theory of communication that emphasises how language is used. By selecting systemic functional linguistics, we can analyse user stories, and have developed a method for factoring unwanted epics into usable user stories

Generating User Stories in Groups

User stories allow customers to easily communicate desired specifications as part of Agile Software Development methods. When elicited from groups instead of individuals, the number of stories generated and the comprehensiveness of the stories is likely to increase. We present a 2 X 2 study design involving group vs. individual user story brainstorming with one or two sentence vs. unlimited user story length

Ethical User stories : Industrial study

Publisher Copyright: © 2022 Copyright for this paper by its authorsIn Port terminals a progressive change is underway in digitalizing traditional systems to SMART systems with the aid of AI. This study follows one of such progressions, the SMARTER project. SMARTER is a sub research and development project of the Sea for Value program of DIMECC company, Finland to create replicable models for digitalization for future terminals which involves the use of AI enabled tools. AI and Autonomous Systems (AS) are the direction that software systems are taking today. But due to ethical challenges involved in the use of AI systems and increased emphasis on ethical practices in the use and design of AI systems, our study provides an ethical angle, Ethical User Stories (EUS). We use an ethically aligned design tool the ECCOLA method to transfer ethical requirements into EUS for non-functional requirements for an aspect of the logistics system, passenger flow. Over the span of six months, 125 EUS using the ECCOLA method were collected through a series of workshops for the passenger flow use case and the findings are revealed in this paper. This project is in the field of maritime industry and concentrates on digitalization of port terminals and this particular paper focuses on the passenger flow. Results are positive towards the practice of Ethical User Stories.Peer reviewe

A Research Agenda on Using Conceptual Models for User Story Development

Agile practitioners and researchers have identified many challenges related to the requirements in agile projects. Some of these challenges relate to documentation and more specifically the development, maintenance, and management of user stories. This research addresses some of the user stories challenges by proposing the use of conceptual models while developing user stories. Conceptual models are presentations used for domain understanding. The proposal considers development of such conceptual models automatically while user stories are developed. A detailed research plan has been developed to conduct this research

Synergistically Employing User Stories and Use Cases in the Practice and Teaching of Systems Analysis and Design

Over the past three decades, user stories and use cases have become increasingly dominant systems analysis and design (SA&D) requirements techniques. Both support articulating functional requirements for software projects, although they evolved within different software development approaches—user stories from agile development and use cases from traditional software engineering—and they differ significantly in terms of their grammar, syntax, and the level of detail they can capture. As such, user stories and use cases are neither synonyms nor mutually exclusive alternatives. Rather, they can and should be complementary in the systems requirements process. Unfortunately, this mix of similarities and differences—coupled with a lack of formal standards for either—make understanding and synergistically employing user stories with use cases confusing and challenging for practitioners and students alike. To address this, this paper first provides a descriptive overview of the evolution of user stories, use cases, and their interrelationship. Second, it fills a gap in the literature by providing a prescriptive, detailed approach to employing user stories and use cases together. This prescriptive approach is illustrated via a comprehensive tutorial example, providing practitioners with actionable skills and SA&D teachers and students with a new pedagogical tool

Requirements engineering and continuous deployment

This article summarizes the RE in the Age of Continuous Deployment panel at the 25th IEEE International Requirements Engineering Conference. It highlights two synergistic points (user stories and linguistic tooling) and one challenge (nonfunctional requirements) in fast-paced, agile-like projects, and recommends how to carry on the dialogue.Peer ReviewedPostprint (author's final draft

Agile user stories enriched with usability

Usability is a critical quality factor. Therefore, like traditional software teams, agile teams have to address usability to properly catch their users experience. There exists an interesting debate in the agile and usability communities about how to achieve this integration. Our aim is to contribute to this debate by discussing the incorporation of particular usability recommendations into user stories, one of the most popular artifacts for communicating agile requirements. In this paper, we explore the implications of usability for both the structure of and the process for defining user stories. We discuss what changes the incorporation of particular usability issues may introduce in a user story. Although our findings require more empirical validation, we think that they are a good starting point for further research on this line

Generating User Stories in Groups with Prompts

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, and with prompts, the number of stories generated and comprehensiveness of the stories is likely to increase. A lab experiment was conducted to examine these hypotheses is delineated in this paper. We found that prompting significantly increased the number of user stories generated as well as the comprehensiveness of the stories generated. We did not find a difference in user stories generated or comprehensiveness of stories generated by groups and individuals

A Systematic and Lightweight Method to Identify Dependencies between User Stories

The order in which user stories are implemented can have a significant influence on the overall development cost. The total cost of developing a system is non commutative because of dependencies between user stories. This paper presents a systematic and lightweight method to identify dependencies between user stories, aiding in the reduction of their impact on the overall project cost. Initial architecture models of the software product are suggested to identify dependencies. Using the method proposed does not add extra load to the project and reinforces the value of the architecture, facilitates the planning and improves the response to changes