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
01 Jan 2010
TL;DR: This work investigates benefits from adopting a standardized Functional Size Measurement (FSM) method, such as COSMIC Function Points, in place of Story Points, and using a Transfer Function that transforms size into effort spent within a particular agile team, defect density prediction can be made using sensitivity analysis.
Abstract: The spreading of agile methodologies in software development raises the question of how to measure requirements once more, as it happened in ‘traditional’ software industry development approaches decades ago. The difference is that requirements are not known in advance but detected as User Stories while iterating and enhancing the software product from one agile ‘Sprint’ to the other. Some authors – promoting best practices for agile software development – propose Story Points to size User Stories (e.g., Scrum, with Story Cards), yet not combined with base project estimation. Story Points are not standardized, thus leading to eventual misconceptions and quantitative differences among practitioners and domains. The uncertainty implied in such approach can therefore propagate to any estimate based on it, not to mention the difficulty in accurately tracing requirements and their variation over the project and across project iterations. This work investigates benefits from adopting a standardized Functional Size Measurement (FSM) method, such as COSMIC Function Points, in place of Story Points. Using a Transfer Function (from the Six Sigma practice) that transforms size into effort spent within a particular agile team, defect density prediction can be made using sensitivity analysis.

11 citations

Proceedings ArticleDOI
01 Apr 2017
TL;DR: Positive and negative user stories are described followed by conclusion and future work about writing user stories by different ways which it may be treated positively or negatively and how it impact on requirement verification.
Abstract: User stories play an important role in extreme programming. Extreme programming is one of the popular processes from agile software development. Agile software development is an emerging method of software development, as compared to traditional approach. The success of software development is based on user stories satisfaction. As requirement engineering is the first phase in software development approach, user stories are written from customer requirements. This paper discusses about writing user stories by different ways which it may be treated positively or negatively and how it impact on requirement verification. User stories examples written in this paper are through experience gained from attendance monitoring project. In this paper first we have given brief idea about user stories with examples, and then we have described positive and negative user stories followed by conclusion and future work.

11 citations

Proceedings ArticleDOI
01 Nov 2017
TL;DR: This paper exploits an alternative searching technique, called the document fingerprints, to retrieve the similar issues from the public repository of project management assets, called JIRA and uses MMRE and Benchmarking class to evaluate the effectiveness and efficiency of the searching algorithm.
Abstract: In Scrum process, there are several techniques for estimating user story points such as planning poker, expert judgment and analogy. The effort estimation might be performed by the inexperienced team members who are unfamiliar with the particular business domain involved. To improve the estimation performance, the historical data of the similar user story points from the previous successful projects are considered useful and guiding as the analogous estimation. In this paper, we exploit an alternative searching technique, called the document fingerprints, to retrieve the similar issues from the public repository of project management assets, called JIRA. We also use MMRE and Benchmarking class to evaluate the effectiveness and efficiency of our searching algorithm. The results show that the document fingerprints technique works reasonably well, especially for the user stories regarding the existing business domain.

11 citations

Patent
15 Jan 2013
TL;DR: In this paper, a computer-implemented method for managing user story requirements includes collecting, by a processor, a plurality of requirements, creating, by the processor, content space specification files that includes the plurality requirements, processing, by processor, the plurality of specification files to generate plurality of content space-based testable units, and managing the requirements to reduce gaps and overlap.
Abstract: A computer-implemented method for managing user story requirements includes collecting, by a processor, a plurality of requirements, creating, by the processor, a plurality of content space specification files that includes the plurality of requirements, processing, by the processor, the plurality of content space specification files to generate a plurality of content space-based testable units, and managing, by the processor, the plurality of requirements to reduce gaps and overlap between individual content space testable units in the plurality of content space-based testable units.

11 citations

Journal ArticleDOI
TL;DR: In this paper, the authors describe a process of creating eHealth components for an integrated care model using an agile software development approach, user-centered design and behavior theory-guided content development.
Abstract: Purpose To describe a process of creating eHealth components for an integrated care model using an agile software development approach, user-centered design and, via the Behavior Change Wheel, behavior theory-guided content development. Following the principles of implementation science and using the SMILe project (integrated care model for allogeneic stem cell transplantation facilitated by eHealth) as an example, this study demonstrates how to narrow the research-to-practice gap often encountered in eHealth projects. Methods We followed a four-step process: (a) formation of an interdisciplinary team; (b) a contextual analysis to drive the development process via behavioral theory; (c) transfer of content to software following agile software development principles; and (d) frequent stakeholder and end user involvement following user-centered design principles. Findings Our newly developed comprehensive development approach allowed us to create a running eHealth component and embed it in an integrated care model. An interdisciplinary team's collaboration at specified interaction points supported clear, timely communication and interactions between the specialists. Because behavioral theory drove the content development process, we formulated user stories to define the software features, which were prioritized and iteratively developed using agile software development principles. A prototype intervention module has now been developed and received high ratings on the System Usability Scale after two rounds of usability testing. Conclusions Following an agile software development process, structured collaboration between nursing scientists and software specialists allowed our interdisciplinary team to develop meaningful, theory-based eHealth components adapted to context-specific needs. Clinical relevance The creation of high-quality, accurately fitting eHealth components specifically to be embedded in integrated care models should increase the chances of uptake, adoption, and sustainable implementation in clinical practice.

11 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