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 published on a yearly basis
Papers
More filters
TL;DR: Zhang et al. as mentioned in this paper proposed a user requirement quality assessment method based on user stories to address incomplete, inconsistent, and inaccurate user requirements, which increase the workload of agile development teams and reduce the efficiency of product function development, ultimately resulting in the inability to respond quickly to user requirements.
Abstract: Agile development processes based on user stories often face issues such as incomplete, inconsistent, and inaccurate user requirements, which increase the workload of agile development teams and reduce the efficiency of product function development, ultimately resulting in the inability to respond quickly to user requirements. This paper proposes a user requirement quality assessment method based on user stories to address these problems. This method relies on the agile development process, constructs a user requirement quality assessment framework, defines a user story model and a user requirement quality model, develops seven user requirement quality assessment criteria, and designs a user requirement quality assessment process. A data experiment exploring the development of smartphone requirements is used to validate the feasibility and effectiveness of the method. The experimental results demonstrate that the method improves user requirement quality to some extent, providing an automated solution for agile development teams to enhance user requirement quality.
2 citations
27 Mar 2018
TL;DR: A grooming process for a Scrum team is proposed that provides a step-wise approach to work breakdown, from customer requirements elicitation to the development of ready work entities using the user story format.
Abstract: At the current unpredictable technical evolution, the market is demanding an increasingly flexibility from companies to adapt to the pace of change in what customers want. The present research was developed in an automotive company, where software teams are pursuing Agile methodologies to coupe with these challenges. Teams use the Scrum framework, however, lack of efficient communication among team members results in poor performance of the product owner and the development team. In an attempt to solve this issue and according to the needs shared by the teams, this paper proposes a grooming process for a Scrum team. It provides a step-wise approach to work breakdown, from customer requirements elicitation to the development of ready work entities using the user story format. This paper describes how agile methods can support requirements engineering in a software project.
2 citations
13 Feb 2007
TL;DR: In this article, the authors argue that eXtreme Programming (XP) currently places insufficient emphasis on problem understanding and propose an approach that offers additional front end analysis based on Soft Systems Methodology (SSM).
Abstract: Software development can be treated as a form of 'problem solving'. The two main activities are then (i) understanding the problem, by analysing the situation to determine relevant requirements; and (ii) solving the problem, by implementing software that takes account of those requirements. This paper argues that eXtreme Programming (XP) currently places insufficient emphasis on problem understanding and proposes an approach that offers additional front end analysis based on Soft Systems Methodology (SSM). The models of SSM are linked to XP through user stories. The first part of the paper outlines the process involved. This is followed by details of an initial investigation of the proposal, involving experimental group projects with undergraduate computing students. The results highlight some of the strengths and weaknesses of the approach, indicating directions for future research.
2 citations
08 Jun 2020
TL;DR: A work-in-progress research model is provided to set these variables in relation and establish a systematic method to uncover answers regarding their correlation and promising insights into the behavior are provided.
Abstract: User stories are popular for conveying requirements in agile software projects. Despite existing quality criteria, authors make formal mistakes that result in “bad” user story quality. If developers have insufficient experience in balancing quality problems, the creation of a shared mental model is impossible, thus increasing the risk of impacts on the project’s success. This article provides a work-in-progress research model to set these variables in relation and establish a systematic method to uncover answers regarding their correlation. Details on the effects support research in agile requirements engineering to gain a better understanding of cognitive processes in the comprehension of user stories. In addition, insights can help to develop design recommendations and AI tools to improve user stories. A first evaluation of the model provides promising insights into the behavior and forms a basis for future research.
2 citations
21 May 2018
TL;DR: This paper proposes a process for modeling in UML a set of "just-enough" requirements and a candidate architecture, ending with aSet of user stories included in a team backlog.
Abstract: Models provide are beneficial when the solution has a perceived complexity, and may be used as a shared understanding when the project is composed by distributed teams. However, the use of models needs contextualization for agile-oriented backlog items. This paper proposes a process for modeling in UML a set of "just-enough" requirements and a candidate architecture, ending with a set of user stories included in a team backlog.
2 citations