scispace - formally typeset
Search or ask a question
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
More filters
Proceedings ArticleDOI
15 Aug 2011
TL;DR: A holistic approach is proposed that supports management of the development progress in geographically distributed agile projects by identifying and co-ordinating the impact of the technical factors on progress, which will provide distributed agile teams with improved awareness of the actual progress of the software.
Abstract: Progress in agile development is determined by the amount of 'working software' produced. Source code versioning, unit testing, continuous integration and acceptance testing (AT) are technical factors that affect the maturity of the software artefects produced. Therefore, development progress is subject to change due to impact of these technical factors (e.g. modifying source code artefects may affect completed user stories). In co-located agile projects, face-to-face interaction is used to share information about changes that may affect development progress. However, in distributed projects, team members find it harder to maintain an awareness of these changes, which affects their understanding of the development progress. This causes them to rely on less accurate progress information and contributes in producing low quality code and unnecessary rework and delays. In this paper, we propose a holistic approach that supports management of the development progress in geographically distributed agile projects by identifying and co-ordinating the impact of the technical factors on progress, which will provide distributed agile teams with improved awareness of the actual progress of the software.

17 citations

Book ChapterDOI
18 Jun 2005
TL;DR: A proxy-customer role resembling RUP's Analyst is introduced and he is equipped with a tool, called UC Workbench, that supports the communication with the customer representatives and the developers.
Abstract: Agile methodologies are based on effective communication with the customer. The ideal case is XP's on-site customer. Unfortunately, in practice customer representatives are too busy to work with the development team all the time. Moreover, frequently there are many of them and each representative has only partial domain knowledge. To cope with this we introduced to our projects a proxy-customer role resembling RUP's Analyst and we equipped him with a tool, called UC Workbench, that supports the communication with the customer representatives and the developers. Analyst collects user stories from customer representatives and ‘translates' them into use cases. UC Workbench contains among other things a use-case editor and a generator of mockups (a mockup generated by UC Workbench animates use-cases and illustrates them with screen designs).

17 citations

Book ChapterDOI
27 Oct 2014
TL;DR: A bottom-up approach based on the User Story Mapping method (USM) is proposed, which provides a federated and common understanding of information throughout the industrial product and process lifecycle and improves capabilities for sharing and reusing this knowledge in collaborative product development.
Abstract: The context and problem of identifying and thereafter representing, analyzing and managing information and knowledge about an organization has always been very crucial to achieve business goals in an efficient and flexible way. Particularly in a PLM context, the issue of information overload is growing in importance. An emergent challenge consists in providing a context-driven access to federated information and knowledge and fostering cross-discipline collaborations between actors to improve quality in product development. This paper highlights key issues for knowledge definition and representation. We propose a bottom-up approach based on the User Story Mapping method (USM). This method is user-centric and leads to the definition of current and/or expected scenarios and processes along with a collaboratively agreed vision. Common concepts and viewpoints are therefore derived and generalized through a process of merging defined roles, activities and usages sequences with a focus on the product content. This bottom-up approach provides a federated and common understanding of information throughout the industrial product and process lifecycle; which combined with appropriate tools and methods, such as questionnaires, standards specifications, knowledge based approaches, etc. results in the definition of the knowledge network and domain and therefore improves capabilities for sharing and reusing this knowledge in collaborative product development. The proposed approach is applied in the context of the FP7 European project LinkedDesign (Linked Knowledge in Manufacturing, Engineering and Design for Next-Generation Production) based on three application scenarios.

17 citations

Posted Content
TL;DR: This paper proposes a software development process to gather the requirement, analyze, design, develop, test and deploy Blockchain applications, based on several Agile practices, such as User Stories and iterative and incremental development based on them.
Abstract: Cryptocurrencies and their foundation technology, the Blockchain, are reshaping finance and economics, allowing a decentralized approach enabling trusted applications with no trusted counterpart. More recently, the Blockchain and the programs running on it, called Smart Contracts, are also finding more and more applications in all fields requiring trust and sound certifications. Some people have come to the point of saying that the "Blockchain revolution" can be compared to that of the Internet and the Web in their early days. As a result, all the software development revolving around the Blockchain technology is growing at a staggering rate. The feeling of many software engineers about such huge interest in Blockchain technologies is that of unruled and hurried software development, a sort of competition on a first-come-first-served basis which does not assure neither software quality, nor that the basic concepts of software engineering are taken into account. This paper tries to cope with this issue, proposing a software development process to gather the requirement, analyze, design, develop, test and deploy Blockchain applications. The process is based on several Agile practices, such as User Stories and iterative and incremental development based on them. However, it makes also use of more formal notations, such as some UML diagrams describing the design of the system, with additions to represent specific concepts found in Blockchain development. The method is described in good detail, and an example is given to show how it works.

16 citations

Proceedings ArticleDOI
04 Jun 2012
TL;DR: A tool is presented that builds an ontology for code and links completed User Stories in natural language with the related code artifacts and contains links to API components that were used to implement the functional tests.
Abstract: User Stories are short feature descriptions from the user's point of view. Functional tests ensure that the feature described by a User Story is fully implemented. We present a tool that builds an ontology for code and links completed User Stories in natural language with the related code artifacts. The ontology also contains links to API components that were used to implement the functional tests. Preliminary results show that these links can be used to recommend reusable test steps for new User Stories.

16 citations


Network Information
Related Topics (5)
Software development
73.8K papers, 1.4M citations
86% related
Component-based software engineering
24.2K papers, 461.9K citations
86% related
Software system
50.7K papers, 935K citations
84% related
Software construction
36.2K papers, 743.8K citations
84% related
Business process
31.2K papers, 512.3K citations
81% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202334
202259
202157
202084
201991
201875