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: A tool is implemented that combines data analytics and developers’ feedback with human-in-the-loop mechanisms to improve effort estimations and elaborate causes for inaccurate estimations going beyond the borders of existing literature.
15 citations
20 Jun 2011
TL;DR: This paper first characterize the kind of inconsistencies arising in web applications requirements and then shows how to isolate them using a model-driven approach and with a set of examples it illustrates the approach.
Abstract: Web applications evolve fast. One of the main reasons for this evolution is that new requirements emerge and change constantly. These new requirements are posed either by customers or they are the consequence of users' feedback about the application. One of the main problems when dealing with new requirements is their consistency in relationship with the current version of the application. In this paper we present an effective approach for detecting and solving inconsistencies and conflicts in web software requirements. We first characterize the kind of inconsistencies arising in web applications requirements and then show how to isolate them using a model-driven approach. With a set of examples we illustrate our approach.
14 citations
01 Jan 2010
TL;DR: In this paper, the authors present a guideline for sizing Agile projects with the COSMIC method, along with a summary of the resulting guideline, and describe the expected requirements format and their measurement practices.
Abstract: Agile became one of the most used ‘buzzwords’ in ICT projects in these recent years but the growing diffusion and interest of its related methods and techniques was not accompanied by the same maturity in sizing and estimation practices. In particular the application of a functional size measurement (FSM) method for sizing requirements is not typical to ”agilists”, preferring to use mostly estimations based on experience and analogy. In such way, one of several drawbacks is a reduced data gathering from projects, not allowing to do (even at a basic level) statistical analysis, for better estimating the proper efforts value for next user story and – as a whole – of the project. This paper describes the reasons why a guideline for sizing Agile projects with the COSMIC method was required, along with a summary of the resulting guideline. Several agile methods are briefly described, more specifically their expected requirements format and their measurement practices.
14 citations
TL;DR: This paper provides distilled practical advice in a context familiar to XP developers describing how you can start getting acceptance test-infected on your project.
Abstract: Acceptance testing is one of the most important XP practices and yet it is often neglected or perceived as “too hard”. But what if acceptance tests were like unit tests? This paper provides distilled practical advice in a context familiar to XP developers describing how you can start getting acceptance test-infected on your project.
14 citations
23 Oct 2004
TL;DR: This panel brings together practitioners and researchers to discuss and offer wisdom on the challenges and opportunities inherent in the practice of XP (Xtreme Programming).
Abstract: One of the core XP (Xtreme Programming) practices is that of the "on-site customer". In the words of Kent Beck (2000) in his book "eXtreme Programming Explained" the intent is that a "real customer must sit with the team, available to answer questions, resolve disputes, and set small-scale priorities" … "someone who will really use the system when it is in production". This panel brings together practitioners and researchers to discuss and offer wisdom on the challenges and opportunities inherent in the practice.
14 citations