User story

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

Comparison of CMM Level 2 and eXtreme Programming

Abstract: Lightweight software development methodologies promise an easy way to deliver products of high quality without excessive cost. On the contrary, classical heavyweight processes are well-defined and proven, but require a lot of effort. Two approaches: eXtreme Programming (XP) and CMM Level 2 have been used in joined industry-academic software projects run at the Poznan University of Technology. Running concurrently those two software approaches allowed us to compare them on the basis of experimental data. After the projects were completed, major risk factors connected with both approaches have been collected and some improvements have been proposed.

Tailoring Usability into Agile Software Development Projects

Abstract: Usability, user interface, and interaction design are among the group of vital, yet mostly overlooked, skills that all software developers require, yet few seem to have. This is just as true of agile developers as it is of traditional developers. This chapter examines both user experience (UEX) and agile software development (ASD) approaches, comparing and contrasting the underlying philosophies and practices of each. Using agile model-driven development (AMDD) as the foundation, it then describes strategies for tailoring UEX into agile methods. It is possible to address UEX concerns on agile projects, but it requires flexibility and a willingness to work together on the part of both UEX and ASD practitioners.

User stories don't help users: introducing persona stories

Abstract: User stories are one of the most popular alternatives to traditional user requirement specifications (see Figure 1). But despite their promising name, user stories are not about – and don’t necessarily help – users at all. In most cases, user stories are written about roles that users adopt and take no account of the needs and behaviours of real users. Were that not indictment enough, user stories suffer from demonstrable flaws in structure and are often written by the wrong people at the wrong time.

System and method for communicating and interfacing between real and virtual environments

Abstract: A human-to-avatar communication environment is disclosed in which a user comes into contact with a life-sized avatar simulating a sales assistant. The avatar communicates with the user to assist with product information, give advice, provide specifications, answer questions, and transact sales. By interacting with the user, the avatar may gather information from the user that indicates the user's interests. The avatar could assist the user by providing information that may include answering questions the user may have about certain products, directing the user to detailed information about the products, informing the user about the product that best suits the user's needs, informing the user of any complementary or popular accessories that go along with the product, helping the user purchase the products, and notifying the retail store's inventory to prepare the product for delivery or pick-up by the user. In addition, the avatar may provide the user with product information which may include information about a specific product, information about a class of products, information used in the sale of a product, a product rating, a product description, a product price, a product's features, a product's peripheral devices, or any other type of information associated with a product. The user could also be provided with information regarding promotions or prizes from an external source (e.g. online, a catalog, an advertisement, etc.) and instructions to redeem the prize at the communication environment. The avatar could then assist the user in redeeming the prize or receiving, for example, a discount offered in a promotion.

Task oriented software understanding

Abstract: The main factors that affect software understanding are the complexity of the problem solved by the program, the program text, the user's mental ability and experience and the task being performed. The paper describes a planning approach solution to the software understanding problem that focuses on the user's task and expertise. First, user questions about software artifacts have been studied and the most commonly asked questions are identified. These questions are organized into a question model and procedures for answering them are developed. Then, the patterns in user questions while performing certain tasks have been studied and these patterns are used to build generic task models. The explanation system uses these task models in several ways. The task model, along with a user model, is used to generate explanations tailored to the user's task and expertise. In addition, the task model allows the system to provide explicit task support in its interface.