User story

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

A Quality Framework for Agile Requirements : A Practitioner’s Perspective

Abstract: Verification activities are necessary to ensure that the requirements are specified in a correct way. However, until now requirements verification research has focused on traditional up-front requirements. Agile or just-in-time requirements are by definition incomplete, not specific and might be ambiguous when initially specified, indicating a different notion of ‘correctness’. We analyze how verification of agile requirements quality should be performed, based on literature of traditional and agile requirements. This leads to an agile quality framework, instantiated for the specific requirement types of feature requests in open source projects and user stories in agile projects. We have performed an initial qualitative validation of our framework for feature requests with eight practitioners from the Dutch agile community, receiving overall positive feedback.

Developing a Tool Supporting XP Process

Abstract: We present the development of XPSwiki, a tool supporting the XP practices for requirement gathering and project management – user stories and the Planning Game. XPSwiki has been developed in Smalltalk using Squeak Swiki technology, and is accessed through the Internet in a user friendly, agile way. It keeps track of multiple projects, each with its releases, iterations, user stories, acceptance tests, and tasks. XPSwiki allows project tracking, and automates documentation generation and metrics collection. It is presently in use in real software development environments.

The Ugly, the Hype and the Good: an assessment of the agile approach

Abstract: Agile methods contain a mix of the best and the worst, plus some ideas of minor importance. Chapter 11 is the concluding assessment, discussing “The Good, the Hype and the Ugly”:

User-Centred Engineering

Abstract: To set out a one-size-fits-all user-centred engineering procedure suitable for all of the many different situations you are likely to meet is, in our opinion, impossible. Similarly, it is not our aim to provide a recipe book, containing step-by-step instructions on how to apply user-centred techniques. The chapters which follow are instead intended to assist you in understanding how user-centred engineering can be applied during software and product development in practice, how key user-centred techniques actually operate, how they can be planned within your project and what points you need to watch out for. This chapter provides an overview of the relationship between various user-centred techniques and how they are integrated into common software development processes.

A gamification approach for distributed agile delivery

Abstract: Large organizations need to be nimble in delivering software solutions for meeting rapidly changing business requirements and technology landscape. Following Agile principles of software development is a natural choice. However, to truly leverage the power of Agile, big organizations need to be able to utilize distributed teams effectively. Agile relies hugely on shared context and awareness among team members and this can become a stumbling block among such geographically dispersed teams. Moreover, in such large projects there is a need for incentivizing quick delivery of user stories so that the teams have a constructive sense of competition and are recognized in-process. Here, we describe a gamification based approach which promotes quicker completion and acceptance of user stories in such distributed Agile projects. Our approach captures important events from the development environment and then helps create project-wide awareness regarding the progress of different teams. A model of earning revenue for faster delivery of user stories is used to determine the leading team at the end of each sprint. This approach has been implemented in an Agile process guidance and awareness workbench that we are piloting within our organization.