User story

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

The UCD Perspective: Before and After Agile

Abstract: In the agile and user-centered design (UCD) communities it is often believed that agile's quick development cycles do not allow time to fully understand our user's needs. In our experience it is just the opposite: agile and UCD methods are not at odds with each other. As more development teams using UCD are finding, the iterative approach to agile is a natural fit for UCD. Though we have day to day challenges, we are successfully demonstrating how two UCD teammates on the agile team can aid in upfront and continual user input.

Using goal net to model user stories in agile software development

Abstract: Agile methodologies use user stories to capture software requirements. This often results in team members over emphasizing their understanding of the goals, without proper incorporation of goals from other stakeholders or customers. Existing UML or other goal oriented modeling methods tend to be overly complex for non-technical stakeholders to properly express their goals and communicate them to the agile team. In this paper, we propose a light weight Goal Net based method to model goal requirements in agile software development process to address this problem. It can be used to decompose complex processes into phased goals, and model low level user stories to high level hierarchy goal structures. Our preliminary analysis and studies in educational software engineering contexts show that it can improve agile team’s group awareness to project goals and, thus, improve team productivity and artifact quality. The proposed approach was evaluated in university level agile software engineering projects. It has achieved an improvement of over 50 percentage points in terms of the proportion of high quality user stories generated by students compared to the standard user story template used in Scrum. Keywords-Agile Software Development; Goal Net; Software Engineering

A Practical Guide to eXtreme Programming

Abstract: From the Book: PrefaceThe principles of extreme programming have changed the way we think about software development.The Need to be Extreme Both business people and software developers often view traditional software development techniques as too slow. Business people view software as a competitive advantage, and a competitive advantage can never be realized too quickly. Software developers believe that their traditional software development processes create too much overhead in their quest to deliver this advantage as quickly as possible. The need to deliver software more quickly caused Kent Beck, Ward Cunningham, and Ron Jeffries to explore the extremes of certain development practices. The first XP project, the Chrysler Comprehensive Compensation system (code name C3), was, on one hand, constrained and, on the other, pushed to its limits. This practice was called "setting the dials to ten." The result was a breakthrough in the software development called XP. Beck was certainly the driving force behind taking this project, and the multitude of others that have followed, to the extreme, and he continues to evolve XP. His vision continues as he asks us to question the basic principles of software engineering. Naturally, many of these principles are being replaced with new and better ones. New principles, such as working with a real live customer instead of a specification, are quickly gaining acceptance in the software community. The idea of creating tests before the software is written is quickly becoming a vital part of every software development process. This book attempts to capture one point in the evolution of XP.We have examined the principles and have created what we believe to be effective practices. As a result, we believe that this short guide serves as a practical one from which to learn XP. We used some of the XP principles to write this book (adapted, of course, for book writing). For example, various things that one of our customers felt we needed to cover were written on index cards and scheduled into the iterations of the book. This book has been continuously integrated and refactored. Hopefully, you, another customer, will like the finished product. Follow Up To obtain the code from the appendix as well as other information about this book and XP in general, we invite you to visit Saorsa Development Inc.'s web site at http://www.saorsa.com

The Benefits and Challenges of Collaborating with User Communities

Abstract: OVERVIEW:User communities are potentially rich sources of new product ideas and innovations. However, accessing these communities brings significant challenges, including how to identify users, how to engage with them, how to integrate user innovations into corporate process, and how to manage intellectual property and other aspects of the relationship. The LEGO Group's experience engaging with user innovators, explored in a longitudinal study of the firm's interactions with independent and corporate-sponsored user communities, illustrates both the challenges and the rewards of collaborating with user communities.