Motivations and measurements in an agile case study

Abstract

With the recent emergence of agile software development technologies, the software community is awaiting sound, empirical investigation of the impacts of agile practices in a live setting. One means of conducting such research is through industrial case studies. However, there are a number of influencing factors that contribute to the success of such a case study. In this paper, we describe a case study performed at Sabre Airline Solutions evaluating the effects of adopting Extreme Programming (XP) practices with a team that had characteristically plan-driven risk factors. We compare the team's business-related results (productivity and quality) to two published sources of industry averages. Our case study found that the Sabre team yielded above-average post-release quality and average to above-average productivity.We discuss our experience in conducting this case study, including specifics of how data was collected, the rationale behind our process of data collection, and what obstacles were encountered during the case study. We also identify four factors that potentially impact the outcome of industrial case studies: availability of data, tool support, co-operative personnel and project status. We believe that recognizing and planning for these factors is essential to conducting industrial case studies, and that this information will be helpful to researchers and practitioners alike.

Position Paper: Towards a Minimalistic Modeling Paradigm

“…In fact, modeling should be driven by the requirements and later engineering phases by both requirements and models. This is similar to Agile software development [5] combined with modeling. If models are created without a special focus on requirements, it is harder to maintain them simple, avoiding details that are not necessary for the requirements.…”

Mapping of Traditional Software Development Methods to Agile Methodology

“…Research work in Agile Estimation was done by Abrahamsson et al [19], William et al [20], and Erickson et al [21]. Their work describes the various agile methods and how these methods can be applied in industry and why these methods are beneficial than traditional.…”

A multi-case study of agile requirements engineering and the use of test cases as requirements

“…Agile development methods strive to be responsive to changing requirements by integrating requirements, design, implementation and testing processes (Sommerville 2005, Layman 2006). Face-to-face communication is prioritised over written requirements documentation and customers are expected to convey their needs directly to the developers (Beck 2001, Ramesh 2010).…”