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 process of transforming user stories into use cases is proposed and the author will be able to benefit from all the work done in the transformation of the models according to the MDA approach.
65 citations
•
18 Aug 2010TL;DR: In this article, a user chooses a predesigned theme script to be applied to the user's assets to automatically create a story with a particular look and feel, and metadata and feature information is automatically gathered from the user assets to personalize the generated story.
Abstract: Automatic story production is implemented by the utilization of theme scripts with user assets to generate a quality finished product with minimum user input or direction. A user chooses a predesigned theme script to be applied to the user's assets to automatically create a story with a particular look and feel. Metadata and feature information, when available, is automatically gathered from the user assets to personalize the generated story. A user can include additional information and/or alter any aspect of the generated story to further personalize the resultant finished product.
63 citations
••
14 Mar 2016TL;DR: This work develops the gamified requirements engineering model GREM that relates gamification, stakeholder engagement, and RE performance, and leads to the hypothesis that competitive game elements are advantageous for RE elicitation, while socialgame elements are favorable for RE phases where cooperation is demanded.
Abstract: [Context & Motivation] Engaging stakeholders in requirements engineering RE influences the quality of the requirements and ultimately of the system to-be. Unfortunately, stakeholder engagement is often insufficient, leading to too few, low-quality requirements. [Question/problem] We aim to evaluate the effectiveness of gamification to improve stakeholder engagement and ultimately performance in RE. We focus on agile requirements that are expressed as user stories and acceptance tests. [Principal ideas/results] We develop the gamified requirements engineering model GREM that relates gamification, stakeholder engagement, and RE performance. To evaluate GREM, we build an online gamified platform for requirements elicitation, and we report on a rigorous controlled experiment where two independent teams elicited requirements for the same system with and without gamification. The findings show that the performance of the treatment group is significantly higher, and their requirements are more numerous, have higher quality, and are more creative. [Contribution] The GREM model paves the way for further work in gamified RE. Our evaluation provides promising initial empirical insights, and leads us to the hypothesis that competitive game elements are advantageous for RE elicitation, while social game elements are favorable for RE phases where cooperation is demanded.
63 citations
••
22 Sep 2011TL;DR: It is shown that such effort estimation works reasonably well if user stories are written in a structured way and if requirements are developed along with the project and only sketched in a rough manner.
Abstract: In this paper, we propose a method for predicting development effort based on user stories. Such approach is well suited for Agile software projects where requirements are developed along with the project and only sketched in a rough manner. We apply the proposed method to two industrial Agile software projects of very different size and structure. We show that such effort estimation works reasonably well if user stories are written in a structured way.
61 citations
••
TL;DR: By drawing on innovation theory it was found that participatory design in agile development bears the characteristics of a successful organizational innovation.
Abstract: – This paper aims to explore a case of customer and user participation in an agile software development project, which produced a tailor‐made information system for workplace support as a step towards a theory of participatory design in agile software development., – Based on an integrated framework for user participation derived from the participatory design literature the research was performed as a case study and semi‐structured, open‐ended interviews were conducted with about a third of the development team and with a representative sample of key players and future users in the customer organization. The interview data were supplemented with company and project documents., – The paper found genuine customer and user participation carried out by onsite customers and by other operational staff in the form of direct and indirect participation and with functional and democratic empowerment. The onsite customers played informative, consultative and participative roles. The analysis revealed that planning games, user stories and story cards, working software and acceptance tests structured the customer and user participation. This form of user participation supported a balance between flexibility and project progress and resulted in a project and a product which were considered a success by the customer and the development organization. The analysis showed that the integrative framework for user participation can also fruitfully be used in a new context to understand what participatory design is and how, when and where it can be performed as an instance of a design process in agile development. As such the paper contributes to an analytical and a design theory of participatory design in agile development. Furthermore the paper explicates why participatory design contributes to the successful completion of the investigated project. By drawing on innovation theory it was found that participatory design in agile development bears the characteristics of a successful organizational innovation. Grounding further explanations in complex adaptive systems theory the paper provides an additional argument why participatory design despite some identified challenges fosters project staff to successfully carry out the agile development project., – The paper presents an exploratory, empirical study of an understudied phenomenon and contributes to theory building.
61 citations