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
Proceedings ArticleDOI
20 Sep 2017
TL;DR: An investigation on how developers use the techniques/methods of the Human Computer Interaction to support them in the writing of user stories finds that some techniques/ methods are used only to unfold functional requirements and not to report aspects regarding the usability and the user experience.
Abstract: Background: User stories are artifacts largely used to describe requirements in agile software development. However, the writing of user stories usually is focused on describing functional aspects of the software, leaving aside non-functional aspects as usability and user experience. Objective: This paper aims to present the findings of an investigation on how developers use the techniques/methods of the Human Computer Interaction to support them in the writing of user stories; and if, in fact, when the developers use them, they add the usability and user experience aspects in the user story description. Method: An experimental study was conducted to catch and understand the participants' rationales of using each technique/method. Results: Based on the participants' notes, a qualitative analysis was carried out, considering the 92 user stories produced by 42 participants. The results have shown that, in most cases, the participants recognized the importance and the role of the techniques/methods in the writing of user stories. Conclusions: As a conclusion, we can pinpoint that some techniques/methods are used only to unfold functional requirements and not to report aspects regarding the usability and the user experience.

5 citations

Proceedings ArticleDOI
28 Sep 2004
TL;DR: This study illustrates how eXtreme Programming is being used as a "good enough" or "minimum" process by software product companies.
Abstract: Companies engaged in software production are deploying a variety of process models to support their product development activity. Whilst most are tailoring existing process models for use in their specific environments, many have begun to use eXtreme Programming (XP) to achieve their development objectives. This study illustrates how XP is being used as a "good enough" or "minimum" process by software product companies.

5 citations

Proceedings Article
20 Sep 2016
TL;DR: The safety story card will create a common problem understanding between the software developers and the safety stakeholders, to ensure that the agile requirements management process encompass the important safety requirements together with required measurements and techniques.
Abstract: Safety stories is a new practice, developed to ensure that the agile requirements management process encompass the important safety requirements together with required measurements and techniques. The safety story card will create a common problem understanding between the software developers and the safety stakeholders. Safety stories are user stories that include one or more safety requirements. If you do not get the safety right it does not matter how well you execute the rest of the project.

5 citations

Proceedings ArticleDOI
01 Sep 2017
TL;DR: This study presents a roadmap to study communication patterns of Kanban teams and believes that the findings of the study will contribute to strengthen the understanding on the topic and will also provide a good comparison of communication pattern of scrum and Kanban Teams.
Abstract: Communication among agile software development teams is knit around the requirements (user stories) and is considered vital for information sharing. Researchers have studied communication among agile teams from various perspectives including team distribution, distance, and communication patterns etc. It is worth noticing here that most of the advances done in this domain are for Scrum teams. However, minimal work has been done on exploring the communication among Kanban teams. Since, software industry is taking a big leap from Scrum to Kanban and this encourages us to investigate and find interesting insights on Kanban teams' communication. Therefore, in this study we present our roadmap to study communication patterns of Kanban teams. We believe that the findings of the study will contribute to strengthen the understanding on the topic and will also provide a good comparison of communication patterns of scrum and Kanban teams.

5 citations

Proceedings ArticleDOI
01 May 2018
TL;DR: This work sets up a forum for agile testers to discuss their challenges, malpractices, and best practices, and conducted an online survey based on the findings from the forum and literature review to identify 15 challenges and best Practices to overcome those 15 challenges.
Abstract: In the agile framework developers and testers are part of a hyper-productive, self-organizing team. Testing scope changes when user stories are added, updated, or deleted. Moreover, test cases need to be re-written or update when user stories change or removed from the sprint, which wastes time and makes agile testers frustrated. Furthermore, the mini-waterfall model adopted within a sprint could develop unwanted stress in agile testers. Despite these challenges little seem to be understood about the challenges faced by agile testers. We fill this gap by closely studying the challenges faced by agile testers in a multinational IT services organization. We first set up a forum for agile testers to discuss their challenges, malpractices, and best practices. We then conducted an online survey based on the findings from the forum and literature review. Through this, we identified 15 challenges and best practices to overcome those 15 challenges. We further conducted a set of interviews with the subject matter expertise to identify a suitable set of solutions such as conducting retrospective in a fun and engaging way, managing story lifecycle using collaborative tools, setting up ground rules for geographically distributed teams, and introducing innovative sprints.

5 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