scispace - formally typeset
Search or ask a question
Topic

User story

About: User story is a research topic. Over the lifetime, 1078 publications have been published within this topic receiving 23717 citations.


Papers
More filters
Journal ArticleDOI
05 Aug 2022-Software
TL;DR: It is identified that the combination of practices in Agile software development have an impact on the communication in the team, project requirements and project priorities, with more practices being adopted correlating with better project outcomes.
Abstract: Agile software development methods were introduced to minimize problems faced using traditional software development approaches. There are several Agile approaches used in developing software projects, these include Scrum, Extreme programming and Kanban. An Agile approach focuses on collaboration between customers and developers and encourages development teams to be self-organizing. To achieve this there are different Agile practices teams choose to use in their projects. Some teams only use one practice whilst others use a combination of practices. The most common practices used are stand-ups, user stories, Burndown chart/Burnup chart, pair programming, Epic and User stories. This paper reports on the analysis of the data collected from people involved in Agile software development teams and identifies that the combination of practices in Agile software development have an impact on the communication in the team, project requirements and project priorities, with more practices being adopted correlating with better project outcomes.

2 citations

Patent
25 Feb 2020
TL;DR: In this article, a man-machine dialogue template is used to describe a dialogue story, simulating a natural dialogue process, and a dialogue management model is trained by using user story data and domain knowledge.
Abstract: The invention discloses a voice interaction method which comprises the following steps of writing a dialogue story, simulating a natural dialogue process, and writing a man-machine dialogue template;preparing language understanding data, classifying possible input statements of a user according to represented intentions, and marking entities contained in the statements; preparing domain languagemodel data for correcting and recognizing the obtained user statements; training the voice recognition capability of a voice recognition module based on an end-to-end model; correcting the statementsrecognized by the voice recognition module in a statement correction module; using the language understanding data to classify and recognize the corrected statements in a language understanding module; and training a dialogue management model of a dialogue management module by using user story data and domain knowledge The invention further discloses a voice interaction system and dialogue equipment which adopt the voice interaction method The complexity of a system architecture model can be effectively reduced, all dialogue possibilities do not need not be pre-defined, enumeration is easy,and the functionality is good

2 citations

01 Jan 2013
TL;DR: This paper has proposed a solution in form of an approach which Integrates Extreme Programming and Quality Function Deployment to improve the requirement elicitation process that helps to prioritize the user stories and categorize the risk involved with theuser stories.
Abstract: Developing software that completely satisfies the customers' expectations is the main goal of Software Development Methodology. To achieve customer satisfaction, the user requirements must be elicited carefully. There are many problems associated with requirement gathering as the customers cannot explain their expectations, also confusions may arise which may lead to misinterpretation. Therefore, there is a need to analyse their expectations into more specific customer requirements. This paper has proposed a solution in form of an approach which Integrates Extreme Programming and Quality Function Deployment to improve the requirement elicitation process that helps to prioritize the user stories and categorize the risk involved with the user stories.

2 citations

Journal ArticleDOI
TL;DR: In this paper , the authors present an approach for using conceptual models in projects while adhering to Agile principles, focusing on projects in which requirements are expressed as user stories that are the main artifacts of the requirements used for software development with Agile methods.
Abstract: Studies on requirements engineering with Agile methods for software development have shown difficulties in managing the quality of the requirements and communicating with users. Some of these studies have proposed conceptual modeling as a solution to these problems. However, the effort that is required to create conceptual models conflicts with Agile values. In this paper, we propose an approach for using conceptual models in projects while adhering to Agile principles. This approach focuses on projects in which requirements are expressed as user stories that are the main artifacts of the requirements used for software development with Agile methods. First, the paper presents a literature review in which we have systematically searched for the challenges to requirements engineering with Agile methods. Next, we report on a survey study in which we interviewed 16 experts in the Agile methodology to confirm the identified challenges and find new ones that are not covered in the literature. Based on a thematic analysis of the challenges, we argue that most of them map to the two main purposes of using conceptual models in software development: improving communication and understanding requirements. To effectively use conceptual models in projects that use the Agile methodology, several conditions must be met, which we make explicit in the paper. The paper ends by illustrating how these conditions can be met demonstrating the models that can be automatically generated from a given set of user stories. This demonstration was subsequently used to obtain feedback from the experts on the perceived benefits of conceptual models in addressing the challenges of requirements engineering.

2 citations

Journal ArticleDOI
TL;DR: In this article , the authors provide paths of reflection on how to integrate a multi-user centered approach to existing user centered design methods and models and provide guidelines for moving from user experience to Multi-User eXperience (MUX) are provided.
Abstract: In recent years, technologies have evolved towards social, universal and collaborative uses involving multiple users. However, methods and models from user centered design are focused on single-user design and do not take into account the impact of other users on intentions and behaviors to use the technology. The objective of this article is to provide paths of reflection on how to integrate a multi-user centered approach to existing user centered design methods and models. Each phase of user-centered design has been rethought to implement this new framework. Guidelines for moving from user experience to Multi-User eXperience (MUX) are provided. In the same way, we recommend adding a multi-user variable in the technology acceptance models to become the Multi-user Acceptance Model (MAM). User research and user testing have also been rethought to a multi-user reach and a multi-user testing. All these considerations are discussed, and lead to a proposal of a future Multi-user Centered Design (MCD) approach, specifically adapted to manage multi-user digital technology development projects. Finally, it is therefore necessary and important to direct research in the fields (acceptance, user experience, user research and user testing) to assist designers with the development of new methods of product design more respectful of social, environmental and collaborative values.

2 citations


Network Information
Related Topics (5)
Software development
73.8K papers, 1.4M citations
86% related
Component-based software engineering
24.2K papers, 461.9K citations
86% related
Software system
50.7K papers, 935K citations
84% related
Software construction
36.2K papers, 743.8K citations
84% related
Business process
31.2K papers, 512.3K citations
81% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202334
202259
202157
202084
201991
201875