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
04 Jan 2012
TL;DR: A 2.5-year field study of how an ASD team for a complex software system adapted the user story concept and the Scrum approach and was able to gain the benefits of ASD - faster development cycles, less documentation, rapid adaptation to insights and conditions.
Abstract: In Agile Software Development (ASD), stakeholders use stories to stimulate conversations that create and convey understanding of software requirements. Some authors have argued that ASD methods have limited applicability to large-scale projects because agile stories are not sufficient to capture the complexities of up-front design. This paper reports a 2.5-year field study of how an ASD team for a complex software system adapted the user story concept and the Scrum approach. The team sought to create a convention for representing agile stories which could capture the complexities of the system requirements without burdening the team with unneeded documentation. They developed eight different ways to represent a story. The core representation of the approach was called a HyperEpic, a structured collection of closely-related HyperStories. HyperEpics required 90-99% fewer words than conventional specifications. Because of their dense form, Hyper-epics were not useful for other phases in the design/build processes. The team evolved a design/build work practice that proceeded in stages. In each stage, stories underwent a one or more transformations. Each transformation represented stories differently to create varied kinds of understandings among different stakeholder sets. The team was able to gain the benefits of ASD -- faster development cycles, less documentation, rapid adaptation to insights and conditions.
21 citations
20 Jun 2011
TL;DR: In this article, an approach moving from the COCOMO (Constructive Cost Model) worked, using the COSMIC measurement method at the micro-level (User Stories) jointly with the quality of the documentation for deploying the functional analysis is proposed.
Abstract: Agile Project Management (APM) is widely used in different software projects from different application domains. APM includes a series of commonly used project management approaches with the intent to handle better uncertainty and unpredictability, which is not always successful. For instance, in a large portion of software projects, accurate planning (and estimating) of whole project lifetime with Agile is difficult. Since a continuously change in (product) requirements occurs as well their incompleteness at the project initialization phase, project plan must be under control and continuously be revised according to its needs and resources. In Agile projects, planning is mainly based on guess estimate of the effort trying to balance the product and the resources not showing the part of each one. In order to improve the guess estimate, this paper proposes an approach moving from the COCOMO (Constructive Cost Model) worked, using the COSMIC measurement method at the micro-level (User Stories) jointly with the quality of the documentation for deploying the functional analysis. The proposed procedure shows that this approach can help the planner to know better why the global effort changes by the time.
21 citations
TL;DR: It is proposed that concise user stories and deliberation can be useful and well-defined focuses for integrating UX work with agile software development without sacrificing their agility.
21 citations
01 Jan 2002
TL;DR: The methodology and techniques used for the elicitation of user requirements as well as how these were in turn transformed into new design solutions are reported on.
Abstract: Who are the users of a cross-language retrieval system? Under what circumstances do they need to perform such multi-language searches? How will the task and the context of use affect successful interaction with the system? Answers to these questions were explored in a user study performed as part of the design stages of Clarity, a EU founded project on cross-language information retrieval. The findings resulted in a rethink of the planned user interface and a consequent expansion of the set of services offered. This paper reports on the methodology and techniques used for the elicitation of user requirements as well as how these were in turn transformed into new design solutions.
21 citations
TL;DR: This work describes an enhanced method of characterizing the end user population, based on categorizing end users according to the ways they represent abstractions, which promises an improved ability to highlight niches of end users with special software engineering capabilities or struggles.
Abstract: Over 64 million Americans used computers at work in 1997, and we estimate this number will grow to 90 million in 2012, including over 55 million spreadsheet and database users and 13 million self-reported programmers. Existing characterizations of this end user population based on software usage provide minimal guidance on how to help end user programmers practice better software engineering. We describe an enhanced method of characterizing the end user population, based on categorizing end users according to the ways they represent abstractions. Since the use of abstraction can facilitate or impede achieving key software engineering goals (such as improving reusability and maintainability), this categorization promises an improved ability to highlight niches of end users with special software engineering capabilities or struggles. We have incorporated this approach into an in-progress survey of end user programming practices.
21 citations