User story

About: User story is a research topic. Over the lifetime, 1078 publications have been published within this topic receiving 23717 citations.

The normap methodology: non-functional requirements modeling for agile processes

Abstract: Agile software development methodologies, such as Scrum, have gained tremendous popularity and proven successful in quickly delivering quality Functional Requirements (FRs). However, agile methodologies have not adequately identified, modeled, and linked Non-Functional Requirements (NFRs) with FRs in early development phases. Researchers agree that NFRs have been generally ignored in conventional methodologies, especially ignored in agile environments. This dissertation develops a conceptual framework for NFR modeling in agile processes. The proposed Non-functional Requirements Modeling for Agile Processes (NORMAP) Methodology investigated the feasibility of identifying, linking, and modeling Agile Loose Cases (ALCs) with Agile Use Cases (AUCs) and Agile Choose Cases (ACCs). AUCs are newly proposed hybrid of use cases and agile user stories. ALCs are proposed—loosely—defined agile NFRs. ACCs are proposed potential solutions (operationalizations) for ALCs. A lightweight adapted version of the NFR Framework was developed including 25 important NFRs selected out of 161 for this study. Further, an enhanced risk-driven agile requirements implementation sequence (NORPLAN) was developed and visualized as a tree-like view (NORVIEW). The NORMAP Methodology was validated through developing NORMATIC--a Java-based agile visual modeling simulation tool and two case studies. NORMATIC utilized Natural Language Processing (NLP) tools to parse requirement sentences and identify potential ALCs. The first case study utilized the Predictor Models in Software Engineering (PROMISE) dataset used in NFRs classification. NORMAP successfully parsed and classified ALCs for 529 out of 607 (87.15%) independent user requirements. The second case study utilized the European Union eProcurement System’s 26 functional requirements. NORMAP successfully parsed and classified ALCs for 50 out of 57 sentences that included possible ALCs (87.71%). Furthermore, requirements quality and project management metrics were used to calculate a risk-driven requirements implementation sequence using three priority schemes. Results showed that Riskiest-Requirements-First priority scheme planned requirements in 17 sprints--two months earlier than the Highest-Business-Value-First scheme (21 sprints) and one month earlier than the Riskiest-Requirements-Last scheme (19 sprints). Agile communities can potentially benefit from the NORMAP Methodology by utilizing a systematic and risk-driven lightweight engineering process to visually model and plan NFRs as first-class artifacts in agile environments.

Transitioning from Agile Development to Enterprise Product Management Agility

Abstract: By now, your company has made the transition to Scrum. "Sprints", "backlogs", and "retrospectives" are everyday words, but you have discovered the complications that arise within Product Management. Product Owners and Managers who have been scattered across multiple teams are no longer in sync, and at the senior management level, there is not very much visibility into what the Scrum teams are working on unless backlogs are scrutinized. Even then, it is difficult to connect the user stories to management’s high level goals. In addition, cross-product dependencies are not being effectively recognized and managed. The necessity of tracing high level business objectives and portfolio initiatives down to the user story level is essential to any high performing agile development organization. This experience report details how Ultimate Software has successfully transitioned from agile development to an agile enterprise.

Intelligent Agent IA Systems to Generate User Stories for a Positive User Experience

Abstract: In User Centered Design UCD approaches within software development processes, understanding of users, tasks and environments identifying needs and establishing requirements for a positive user experience UX is essential to achieve a high usability The quantitative measurement of UX relies on the fulfillment of psychological needs that can be addressed in storyboards in order to create a context for a certain experience with a particular application To facilitate the process of capturing software products functionality, we present in this work a framework based on Intelligent Agent IA systems to semi-automatically generate user stories A strong story line is guaranteed by a character-centric approach and additional supportive agents that are defined through characters' properties in form of needs, behaviors skills and goals Moreover, we allow for the storage of the created characters into a database, so that they can be reused for further stories and we perform a usability evaluation on the user interface to ensure that it meets users' expectations The system was classified as easy to use and suitable to perform the intended tasks and it also met users' expectation

Variability and Commonality Requirement Specification on Agile Software Development: Scrum, XP, Lean, and Kanban

Abstract: The user story widely studied insufficiently describes the software requirements. Many studies discuss the challenges of requirements specifications and proposed solutions. However, there are many agile methods and each method embraces different practices. Therefore, the solution has to follow each method’s ceremonies. Only a few studies discuss conducted practices in requirements specification development with the agile method and there are no studies that discuss practices comparisons among these methods. In this paper, we performed a systematic literature review to gather the available studies in procuring a current insight into the requirements engineering practices incorporate into the agile method. This study aims to map the variability and commonality practices among agile methods. The various and standard agile RE practices show crucial practices in the requirements specification development process. Moreover, it gives information on practices from other methods that increase the success of requirements specification development. From the systematic literature review, we found a total of 12 studies relevant to the study. There are eight variability and commonality practices between Scrum, XP, and Lean methods.