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
01 Jan 1995
TL;DR: Information Technology is a special kind of artifact, in relation to its use by human users, where users need to construct their own mental representations of the underlying complexity, in order to plan their use, to execute task delegation, and to interpret the actions of the system.
Abstract: Information Technology is a special kind of artifact, in relation to its use by human users. IT systems and IT applications are characterised by a very complex structure, even if we restrict our focus to those parts of IT that an “end user” needs to understand in using it. At the same time the very nature of IT prohibits direct observation of the complexity of the processes and data structures that are relevant for the user. Consequently, users need to construct their own mental representations of the underlying complexity, in order to plan their use, to execute task delegation, and to interpret the actions of the system.
3 citations
01 Jan 2011
TL;DR: A development team from the Kojack Games Company delivers a new and exciting product that will be implemented using agile development methods: Scrum for project management and eXtreme Programming for the day-to-day work.
Abstract: Welcome to Kojack Games! Over the next five chapters you will be watching a development team from the Kojack Games Company You will watch as this team delivers a new and exciting product that will be implemented using agile development methods: Scrum for project management and eXtreme Programming for the day-to-day work
3 citations
01 Jan 2018
TL;DR: This paper attempts to prioritize acceptance tests in order to identify critical tests and demonstrates the applicability and effectiveness of the proposed approach with the help of a realistic example.
Abstract: User stories that are the requirements engineering artifacts in agile software development must be accepted by the end user before being implemented. Acceptance testing is used to confirm the acceptance of user stories. User story acceptance tests are driven by user-defined acceptance criteria. The number of acceptance tests increases as the application size increases. One of the prominent reasons for adopting agile software development is quicker delivery of working software. In this paper, we attempt to prioritize acceptance tests in order to identify critical tests. Execution of critical acceptance tests is sufficient to satisfy the acceptance criteria for a user story and reduces the time to delivery of software. Prioritization of acceptance tests is realized by application of meta-heuristic techniques, i.e., genetic algorithm (GA), cuckoo search algorithm, and micro-GA algorithm. The information flow (IF) model is used as a basis of fitness function to ensure maximum coverage of user acceptance criteria. We demonstrate the applicability and effectiveness of the proposed approach with the help of a realistic example. A comparative analysis of the application of meta-heuristic techniques is performed to choose the best one.
3 citations
01 Dec 2020
TL;DR: In this paper, the authors explored the role, efficiency and efficacy of spikes in various software development domains through the different agile methods and found that spikes have become an essential tool for most agile teams in ASD.
Abstract: Spikes can be an essential component of the agile development cycle, because they assist the teams, for both technical and functional issues, to identify any uncertainty in a user story, leading to a more efficient solution to the problem. The use of spikes in agile software development (ASD) can enable organizations to produce quality software by employing the required technical expertise, planning the entire development cycle and ensuring that the client’s requirements are adhered to. This study aims to examine the use of spikes in ASD. It explores the role, efficiency and efficacy of spikes in various software development domains through the different agile methods. An exploratory research design is adopted to achieve this purpose, whereby mixed methods are used to collect concurrently both qualitative and quantitative data from the experts recruited to the study. Through the survey, it establishes that the primary role of spikes is risk management through investigations to understand user stories and reveal any uncertainty. Conclusively, the study findings imply that spikes have become an essential tool for most agile teams in ASD. The efficiency and effectiveness that are reported show that the majority of experts in software development have realized the value of using spikes in their processes.
3 citations
[...]
01 Jan 2019
TL;DR: The definition of done (DOD) is an agreement within the team that defines what must be completed for each user story in order to be presented at a sprint review with the product owner.
Abstract: The definition of done (DOD) is a fundamental element of any agile project that helps maintain quality and limit scope. It is an agreement within the team that defines what must be completed for each user story in order to be presented at a sprint review with the product owner. Definition of done can be applied to epics, user stories, and tasks using unique criteria to define when each is “done.” The DOD can be extended to each agile including sprint planning, sprint demos, retrospectives, and backlog grooming in order to achieve team agreement that each ceremony is complete. In that case, the DOD defines the tasks and work items required to complete each agile ceremony.
3 citations