The impact of agile practices on communication in software development

Minna Pikkarainen (Corresponding Author), Jukka Haikara, Outi Salo, Pekka Abrahamsson, J. Still

Research output: Contribution to journalArticleScientificpeer-review

158 Citations (Scopus)

Abstract

Agile software development practices such as eXtreme Programming (XP) and SCRUM have increasingly been adopted to respond to the challenges of volatile business environments, where the markets and technologies evolve rapidly and present the unexpected. In spite of the encouraging results so far, little is known about how agile practices affect communication. This article presents the results from a study which examined the impact of XP and SCRUM practices on communication within software development teams and within the focal organization. The research was carried out as a case study in F-Secure where two agile software development projects were compared from the communication perspective. The goal of the study is to increase the understanding of communication in the context of agile software development: internally among the developers and project leaders and in the interface between the development team and stakeholders (i.e. customers, testers, other development teams). The study shows that agile practices improve both informal and formal communication. However, it further indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication. The study highlights the fact that hurdles and improvements in the communication process can both affect the feature requirements and task subtask dependencies as described in coordination theory. While the use of SCRUM and some XP practices facilitate team and organizational communication of the dependencies between product features and working tasks, the use of agile practices requires that the team and organization use also additional plan-driven practices to ensure the efficiency of external communication between all the actors of software development.
Original languageEnglish
Pages (from-to)303-337
Number of pages34
JournalEmpirical Software Engineering
Volume13
Issue number3
DOIs
Publication statusPublished - 2008
MoE publication typeA1 Journal article-refereed

Fingerprint

Software engineering
Communication
Computer programming

Cite this

Pikkarainen, Minna ; Haikara, Jukka ; Salo, Outi ; Abrahamsson, Pekka ; Still, J. / The impact of agile practices on communication in software development. In: Empirical Software Engineering. 2008 ; Vol. 13, No. 3. pp. 303-337.
@article{8db8072a5f614725a305d68b3064360a,
title = "The impact of agile practices on communication in software development",
abstract = "Agile software development practices such as eXtreme Programming (XP) and SCRUM have increasingly been adopted to respond to the challenges of volatile business environments, where the markets and technologies evolve rapidly and present the unexpected. In spite of the encouraging results so far, little is known about how agile practices affect communication. This article presents the results from a study which examined the impact of XP and SCRUM practices on communication within software development teams and within the focal organization. The research was carried out as a case study in F-Secure where two agile software development projects were compared from the communication perspective. The goal of the study is to increase the understanding of communication in the context of agile software development: internally among the developers and project leaders and in the interface between the development team and stakeholders (i.e. customers, testers, other development teams). The study shows that agile practices improve both informal and formal communication. However, it further indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication. The study highlights the fact that hurdles and improvements in the communication process can both affect the feature requirements and task subtask dependencies as described in coordination theory. While the use of SCRUM and some XP practices facilitate team and organizational communication of the dependencies between product features and working tasks, the use of agile practices requires that the team and organization use also additional plan-driven practices to ensure the efficiency of external communication between all the actors of software development.",
author = "Minna Pikkarainen and Jukka Haikara and Outi Salo and Pekka Abrahamsson and J. Still",
year = "2008",
doi = "10.1007/s10664-008-9065-9",
language = "English",
volume = "13",
pages = "303--337",
journal = "Empirical Software Engineering",
issn = "1382-3256",
publisher = "Springer",
number = "3",

}

The impact of agile practices on communication in software development. / Pikkarainen, Minna (Corresponding Author); Haikara, Jukka; Salo, Outi; Abrahamsson, Pekka; Still, J.

In: Empirical Software Engineering, Vol. 13, No. 3, 2008, p. 303-337.

Research output: Contribution to journalArticleScientificpeer-review

TY - JOUR

T1 - The impact of agile practices on communication in software development

AU - Pikkarainen, Minna

AU - Haikara, Jukka

AU - Salo, Outi

AU - Abrahamsson, Pekka

AU - Still, J.

PY - 2008

Y1 - 2008

N2 - Agile software development practices such as eXtreme Programming (XP) and SCRUM have increasingly been adopted to respond to the challenges of volatile business environments, where the markets and technologies evolve rapidly and present the unexpected. In spite of the encouraging results so far, little is known about how agile practices affect communication. This article presents the results from a study which examined the impact of XP and SCRUM practices on communication within software development teams and within the focal organization. The research was carried out as a case study in F-Secure where two agile software development projects were compared from the communication perspective. The goal of the study is to increase the understanding of communication in the context of agile software development: internally among the developers and project leaders and in the interface between the development team and stakeholders (i.e. customers, testers, other development teams). The study shows that agile practices improve both informal and formal communication. However, it further indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication. The study highlights the fact that hurdles and improvements in the communication process can both affect the feature requirements and task subtask dependencies as described in coordination theory. While the use of SCRUM and some XP practices facilitate team and organizational communication of the dependencies between product features and working tasks, the use of agile practices requires that the team and organization use also additional plan-driven practices to ensure the efficiency of external communication between all the actors of software development.

AB - Agile software development practices such as eXtreme Programming (XP) and SCRUM have increasingly been adopted to respond to the challenges of volatile business environments, where the markets and technologies evolve rapidly and present the unexpected. In spite of the encouraging results so far, little is known about how agile practices affect communication. This article presents the results from a study which examined the impact of XP and SCRUM practices on communication within software development teams and within the focal organization. The research was carried out as a case study in F-Secure where two agile software development projects were compared from the communication perspective. The goal of the study is to increase the understanding of communication in the context of agile software development: internally among the developers and project leaders and in the interface between the development team and stakeholders (i.e. customers, testers, other development teams). The study shows that agile practices improve both informal and formal communication. However, it further indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication. The study highlights the fact that hurdles and improvements in the communication process can both affect the feature requirements and task subtask dependencies as described in coordination theory. While the use of SCRUM and some XP practices facilitate team and organizational communication of the dependencies between product features and working tasks, the use of agile practices requires that the team and organization use also additional plan-driven practices to ensure the efficiency of external communication between all the actors of software development.

U2 - 10.1007/s10664-008-9065-9

DO - 10.1007/s10664-008-9065-9

M3 - Article

VL - 13

SP - 303

EP - 337

JO - Empirical Software Engineering

JF - Empirical Software Engineering

SN - 1382-3256

IS - 3

ER -