Embracing change with extreme programming

Beck, Kent

doi:10.1109/2.796139

Cited by 776 publications

(642 citation statements)

References 2 publications

Supporting

Mentioning

429

Contrasting

Unclassified

Order By: Relevance

“…Plan-driven approaches are still relevant today as they are widely used in practice as recognized in many research articles (c.f. [Raccoon(1997), Beck(1999), Laplante and Neill(2004), Dai and Guo(2007)]). The case company of this study used the approach till 2005, and there are still new research publications on plan-driven approaches (cf.…”

Section: Plan-driven Developmentmentioning

confidence: 99%

The effect of moving from a plan-driven to an incremental software development approach with agile practices

2010

View full text Add to dashboard Cite

So far, only few in-depth studies focused on the direct comparison of process models in general, and between plan-driven and incremental/agile approaches in particular. That is, it is not made explicit what the effect is of moving from one model to another model. Furthermore, there is limited evidence on advantages and issues encountered in agile software development, this is specifically true in the context of large-scale development.Objectives: The objective of the paper is to investigate how the perception of bottlenecks, unnecessary work, and rework (from hereon referred to as issues) changes when migrating from a plan-driven to an incremental software development approach with agile practices (flexible product backlog, face-to-face interaction, and frequent integration), and how commonly perceived these practices are across different systems and development roles. The context in which the objective should be achieved is largescale development with a market-driven focus. The selection of the context was based on the observation in related work that mostly small software development projects were investigated and that the investigation was focused on one agile model (eXtreme programming).Research Method: A case study was conducted at a development site of Ericsson AB, located in Sweden in the end of 2007. In total 33 interviews were conducted in order to investigate the perceived change when migrating from plan-driven to incremental and agile software development, the interviews being the primary source of evidence. For triangulation purposes measurements collected by Ericsson were considered, the Author One School 1 Institute 1 Address 1 Institute 2 Address Tel.: 00-10-00000000 E-mail: mail@domain.com Author Two School Institute Aaddress 2 measurements relating to unnecessary work (amount of discarded requirements) and rework (data on testing efficiency and maintenance effort). Triangulation in this context means that the measurements were used to confirm the perceived changes with an additional data source.Results: In total 64 issues were identified, 24 being of general nature and the remaining 40 being local and therefore unique to individual's opinions or a specific system. The most common ones were documented and analyzed in detail. The commonality refers to how many persons in different roles and across the systems studied have mentioned the issues for each of the process models. The majority of the most common issues relates to plan-driven development. We also identified common issues remaining for agile after the migration, which were related to testing lead-time, test coverage, software release, and coordination overhead. Improvements were identified as many issues commonly raised for the plan-driven approach were not raised anymore for the incremental and agile approach.Conclusion: It is concluded that the recent introduction (start in 2005 with the study being conducted in the end of 2007) of incremental and agile practices brings added values in comparison to the plan-driven approach, whi...

show abstract

Section: Plan-driven Developmentmentioning

confidence: 99%

The effect of moving from a plan-driven to an incremental software development approach with agile practices

2010

View full text Add to dashboard Cite

show abstract

“…XP evolved from the problems caused by the long development cycles of traditional development models [21].…”

Section: Agile Practicesmentioning

confidence: 99%

An agile process model for product derivation in software product line engineering

O’Leary

McCaffery

Thiel

et al. 2012

J Software Evolu Process

View full text Add to dashboard Cite

Abstract. Software Product Lines (SPL) and Agile practices have emerged as new paradigms for developing software. Both approaches share common goals; such as improving productivity, reducing time to market, decreasing development costs and increasing customer satisfaction. These common goals provide the motivation for this research. We believe that integrating Agile practices into SPL can bring a balance between agility and formalism. However, there has been little research on such integration. We have been researching the potential of integrating Agile approaches in one of the key SPL process areas, product derivation. In this paper we present an outline of our Agile process model for product derivation that was developed through industry based case study research.

show abstract

“…Software development methodologies ( [1], [2], [3], [4], [7]) were proposed as tools to decrease complexity, by providing methods to elaborate each aspect involved in the application development. However, the weakest link in all those methodologies is the transition between phases: there are no established methods indicating what to do with the software artifacts generated in one step when moving to the next one.…”

Section: Introductionmentioning

confidence: 99%

From Analysis Model to Software Architecture: A PIM2PIM Mapping

Pérez

Sierra-Alonso

2006

Model Driven Architecture – Foundations and Applications

View full text Add to dashboard Cite

Abstract. To our knowledge, no current software development methodology explicitly describes how to transit from the analysis model to the software architecture of the application. This paper presents a method to derive the software architecture of a system from its analysis model. To do this, we are going to use MDA. Both the analysis model and the architectural model are PIMs described with UML 2. The model type mapping designed consists of several rules (expressed using OCL and natural language) that, when applied to the analysis artifacts, generate the software architecture of the application. Specifically the rules act on elements of the UML 2 metamodel (metamodel mapping). We have developed a tool (using Smalltalk) that permits the automatic application of these rules to an analysis model defined in Rose to generate the application architecture expressed in the architectural style C2.

show abstract

Embracing change with extreme programming

Cited by 776 publications

References 2 publications

The effect of moving from a plan-driven to an incremental software development approach with agile practices

The effect of moving from a plan-driven to an incremental software development approach with agile practices

An agile process model for product derivation in software product line engineering

From Analysis Model to Software Architecture: A PIM2PIM Mapping

Contact Info

Product

Resources

About