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
•
IBM1
TL;DR: One or more test results and one or more user stories are received as mentioned in this paper, and each test result in the test results is compared to a set of content space coordinates of the user stories.
Abstract: One or more test results and one or more user stories are received. For each test result in the one or more test results a set of content space coordinates of the one or more test results is compared to a set of content space coordinates of the one or more user stories. Based on the comparison it is determined if one or more user stories have been tested. One or more results of the comparison are then stored.
8 citations
••
TL;DR: Use-Case 2.0 as mentioned in this paper is the new generation of use-case-driven development-light, agile, and lean-inspired by user stories and the agile methodologies Scrum and Kanban.
Abstract: Use cases have been around for almost 30 years as a requirements approach and have been part of the inspiration for more-recent techniques such as user stories. Now the inspiration has flown in the other direction. Use-Case 2.0 is the new generation of use-case-driven development-light, agile, and lean-inspired by user stories and the agile methodologies Scrum and Kanban.
8 citations
•
8 citations
•
30 Jul 2000
TL;DR: The benefits available from adopting XP style unit testing on a project are discussed, and useful lessons that can be learned from other XP practices are identified.
Abstract: Although Kent Beck has explained eXtreme Programming, there are many benefits to adopting eXtreme Programming (XP) practices in other development processes. The benefits of adopting the complete XP approach are outside of the scope of this paper, what is discussed here are the lessons that XP offers to other development processes.This paper initially discusses the benefits available from adopting XP style unit testing on a project, and then moves on to identify useful lessons that can be learned from other XP practices. The paper concludes by asking questions about the nature of process improvement in software development and how we can make our software serve society.
8 citations
••
22 Jun 2015TL;DR: Experiments evidence that BPMN models improve quality and quantity of information collected during requirements elicitation and ease that clients specify clearly their needs and business goals.
Abstract: Many communication problems may appear during requirements elicitation causing that final products do not accomplish client expectations. This paper analyzes the impact of using business processes management notation (BPMN) instead of user stories during requirements analysis in agile methodologies. For analyzing the effectiveness of our approach, we compare the use of user stories vs. BP models in eleven software projects during requirements elicitation phase. Experiments evidence that BPMN models improve quality and quantity of information collected during requirements elicitation and ease that clients specify clearly their needs and business goals.
8 citations