Loading...

Media is loading
 

Description

Although agile software development (ASD) is widespread, thecontributions of individual agile practices to development success are still largelyunclear. In this paper, we explore the hidden cause-effect relationships betweenthe application of social agile practices, the realization of social agile principles,and the resulting contribution(s) to ASD success. To capture ASD success, weconsider both the effects on developer acceptance and economic business values.Based on an initial ASD success model and data from a survey of 197 developers,we found that social agile practices such as reflection, business IT alignment, andself-organization seem to particularly promote ASD success. We also foundindications that the realization of these principles is primarily driven by practicessuch as retrospective meetings and shared leadership, whereas prominentpractices like daily meetings and pair programming seem to have no effect. Ourresults thus call for reassessment of agile practices and their use in practice.

Share

COinS
 
Jan 17th, 12:00 AM

How Do Individual Social Agile Practices Influence the Development Success? An Exploratory Study

Although agile software development (ASD) is widespread, thecontributions of individual agile practices to development success are still largelyunclear. In this paper, we explore the hidden cause-effect relationships betweenthe application of social agile practices, the realization of social agile principles,and the resulting contribution(s) to ASD success. To capture ASD success, weconsider both the effects on developer acceptance and economic business values.Based on an initial ASD success model and data from a survey of 197 developers,we found that social agile practices such as reflection, business IT alignment, andself-organization seem to particularly promote ASD success. We also foundindications that the realization of these principles is primarily driven by practicessuch as retrospective meetings and shared leadership, whereas prominentpractices like daily meetings and pair programming seem to have no effect. Ourresults thus call for reassessment of agile practices and their use in practice.