Toward a framework for evaluating extreme programming

Williams, Laurie; Krebs, William K.; Layman, Lucas; Antón, Annie I.

doi:10.1049/ic:20040394

Cited by 44 publications

(43 citation statements)

References 47 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…A more detailed discussion of the XP-EF, its creation, rationale, and shortcomings may be found in [21]. Instructions and templates for measuring and reporting XP case study data via XP-EF Version 1.4 have been documented in [20].…”

Section: Extreme Programming Evaluation Frameworkmentioning

confidence: 99%

“…A year-long case study was performed with a small team (7-11 team members) at IBM to assess the effects of adopting XP [21]. The case study was structured using the XP-EF.…”

Section: Xp Studiesmentioning

confidence: 99%

“…An automated means of collecting these metrics is currently unavailable, though one suggested method involves examining comment banners to identify changes done by pair programmers rather than by solo programmers [22]. Manually tracking the amount of time spent pairing when working on a user story would be elementary, but would be tedious in that developers would have to record information every time that they worked on a specific item.…”

Section: Coding Practice Adherencementioning

confidence: 99%

“…For instance, in our case studies of XP practices [16,21], we record context information about the team and project under study, we measure the team's usage of XP practices, and we measure the business-related results (such as productivity and quality) of the project. However, data collection and software process measurement are not simple tasks.…”

Section: Introductionmentioning

confidence: 99%

“…This paper discusses the process of conducting an industrial case study with an agile team at Sabre Airline Solutions. In order to facilitate data collection and to guide our agile case studies, we have created the Extreme Programming Evaluation Framework (XP-EF) [21]. We discuss our rationale behind the processes for collecting certain metrics so that we can create a methodologically defensible case study.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Motivations and measurements in an agile case study

Layman

Williams

Cunningham

2006

Journal of Systems Architecture

View full text Add to dashboard Cite

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.

show abstract

Section: Extreme Programming Evaluation Frameworkmentioning

confidence: 99%

“…A year-long case study was performed with a small team (7-11 team members) at IBM to assess the effects of adopting XP [21]. The case study was structured using the XP-EF.…”

Section: Xp Studiesmentioning

confidence: 99%

Section: Coding Practice Adherencementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Motivations and measurements in an agile case study

Layman

Williams

Cunningham

2006

Journal of Systems Architecture

View full text Add to dashboard Cite

show abstract

Maturing in Agile: What Is It About?

Fontana

Reinehr

Malucelli

2014

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. Maturity in agile software development is a subject still in definition. Although a number of models have been proposed, they usually adapt agile practices to CMMI-DEV requirements or differ among authors. The objective of this study was to identify how agile practitioners define a road map to maturity. We conducted a survey with Brazilian agilists and analyzed data using statistical Chi-square method. Our findings suggest that practitioners' opinion is that a prescribed model to agile maturity would not be useful -we propose, then, an initial guide for maturity. This guide defines some essential practices, but space should be left for teams to do the job as they please.

show abstract

Agility Measurements Mismatch: A Validation Study on Three Agile Team Assessments in Software Engineering

Chronis

Gren

2016

Agile Processes, in Software Engineering, and Extreme Programming

View full text Add to dashboard Cite

Abstract. Many tools have been created for measuring the agility of software teams, thus creating a saturation in the field. Three agile measurement tools were selected in order to validate whether they yield similar results. The surveys of the tools were given to teams in Company A (N = 30). The questions were grouped into agile practices which were checked for correlation in order to establish convergent validity. In addition, we checked whether the questions identified to be the same among the tools would be given the same replies by the respondents. We could not establish convergent validity since the correlations of the data gathered were very few and low. In addition, the questions which were identified to have the same meaning among the tools did not have the same answers from the respondents. We conclude that the area of measuring agility is still immature and more work needs to be done. Not all tools are applicable to every team but they should be selected on the basis of how a team has transitioned to agile.

show abstract

Toward a framework for evaluating extreme programming

Abstract: Abstract

Cited by 44 publications

References 47 publications

Motivations and measurements in an agile case study

Motivations and measurements in an agile case study

Maturing in Agile: What Is It About?

Agility Measurements Mismatch: A Validation Study on Three Agile Team Assessments in Software Engineering

Contact Info

Product

Resources

About