User story

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

An agile approach to requirement specification

Abstract: This experience report is about how one project in Norway made an agile approach to specifying software requirements for a new intranet. Rather than spending months on trying to detail all requirements and aspects of the solution, the team spent a few weeks specifying a prioritized list of high-level requirements. Further details will emerge by face-to-face communication through the iterations of the project quickly turning in to valuable working software for the customer.

Adapting SCRUM to the Italian Army: Methods and (Open) Tools

Abstract: Many software-related technologies, including software development methodologies, quality models, etc. have been developed due to the huge software needs of the Department of Defense (DoD) of the United States. Therefore, it is not surprising that the DoD is promoting open source software and agile approaches into the development processes of the defense contractors. The quality of many open source product has been demonstrated to be comparable to the close source ones and in many cases even higher and the effectiveness of agile approaches has been demonstrated in many industrial settings. Moreover, the availability of the source code makes open source products attractive for obvious reasons (e.g., security, long term maintenance, etc.). Following this trend, also the Italian Army has started using open source software and promotes its usage into the development processes of its contractors, also promoting agile approaches in many contexts focusing on the SCRUM methodology. This paper provides an overview of the SCRUM development process adopted by the Italian Army for the development of software systems using open source technologies.

How user experience is understood

Abstract: There have been many attempts to understand the phenomenon of user experience (UX), but a widely accepted theory is still missing. In this paper we present the results of our investigations on the practical and multidimensional side of user experience. We have studied how professional designers and novices with different backgrounds understand user experience. According to our findings there are three important user experience components: user, product and company. User is perceived to be in the center of user experience among professionals. The importance of user's feelings as part of a holistic user experience is emphasized. For novice designers experiences concerning the use of a product are more important than user's feelings. Technical solutions provided by a company, cultural matters and customer feedback are factors to be considered when targeting a holistic user experience.

Prioritising user stories in agile environment

Abstract: In the last few years Agile methodologies appeared as a reaction to traditional software development methodologies. In Agile environment the requirements from the client are always taken in the form of user-stories and prioritization of requirements is done by Moscow method, validate learning and walking skeleton methods. By literature survey it has been observed that these methods are not efficient because they do not consider importance of user-stories by client. In this research work some importance related and effort related factors are considered on the basis of which the prioritization of user-stories is done. Further the feasibility of work has been validated by a case study of Enable Quiz which is a lightweight technical quizzing solution; for companies that hire engineers. The research work will allows the companies to better screen job candidates and assess their internal talent for skills development.

Supporting Program Comprehension in Agile with Links to User Stories

Abstract: Agile software development involves continuously making iterative and incremental changes to source code. When making changes, developers quickly focus on parts of code that they consider to be important, and sometimes miss other relevant parts. Therefore, tool support is needed to help developers locate conceptually related sections of code. In this paper, we present Zelda, a tool designed to work with Agile practices that captures and maintains links between high-level information and source code. We evaluated Zelda with a pilot study where subjects were required to make a change to a small web application (10KLOCs). They were given a task description either on paper or in Zelda. We found that the Zelda Group made more accurate changes, were less likely to become disoriented, and were more willing to access additional information.