The impact of agile practices on communication in software development

Empirical Software Engineering

Volumn 13, Issue 3, 2008, Pages 303-337

  Pikkarainen, M ^a   Haikara, J ^b   Salo, O ^a   Abrahamsson, P ^a   Still, J ^c  

^a VTT TECHNICAL RESEARCH CENTRE OF FINLAND   (Finland)

^b Polar Electro Oy   (Finland)

^c F Secure Corporation   (Finland)

Author keywords

Agile software development practices; Communication; Coordination theory

Indexed keywords

AGILE MANUFACTURING SYSTEMS; COMMUNICATION SYSTEMS; COMPUTER SUPPORTED COOPERATIVE WORK; PROJECT MANAGEMENT; TECHNOLOGY TRANSFER;

AGILE SOFTWARE DEVELOPMENT PRACTICES; COORDINATION THEORY; EXTREME PROGRAMMING (XP);

SOFTWARE ENGINEERING;

EID: 46549090019     PISSN: 13823256     EISSN: 15737616     Source Type: Journal    
DOI: 10.1007/s10664-008-9065-9     Document Type: Article

References (65)

1. Abrahamsson P, Salo O, Ronkainen J, Warsta J (2002) Agile software development methods: review and analysis. Espoo 107. VTT Publications 408. Espoo
2. Anderson DJ (2003) Agile management for software engineering, applying the theory and constraints for business results. Prentice Hall, Upper Saddle River, NJ
3. Bacharach SB (1989) Organizational theories: some criteria for evaluation. Acad Manage Rev 14(4):496-515
4. Beck K (1999) Embracing change with extreme programming. IEEE Comput 32(10):70-77
5. Beck K (2000) Extreme programming explained: embrace change. Addison-Wesley Longman, Boston, MA
6. Beck K, Andres C (2004) Extreme programming explained, embrace change, 2nd edn. Addison-Wesley, Boston, MA
7. Beck K, Beedle M, Bennekum van A, Cockburn A, Cunningham W, Fowler M, Grenning J, Highsmith J, Hunt A, Jeffries R, Kern J, Marick B, Martin R, Mellor S, Schwaber K, Sutherland J, Thomas D (2001) Manifesto for agile software development. Availale at: http://AgileManifesto.org. Accessed 17.7.2007
8. Boehm B (2003) Value based software engineering, AC, SieSoft, Software Engineering Notes, Vol 28, nro 2, p. 1-12
9. Boehm B, Turner D (2003) Using risk to balance agile and plan-driven methods. IEEE Comput 36(6):57-66
10. Boehm B, Turner D (2005) Management challenges to implement agile processes in traditional development organizations. IEEE Softw 22(5):30-38
11. Boehm BW, Ross R (1989) Theory-W software project management principles and examples. IEEE Trans Softw Eng 15(7):902-916
12. Börjesson A, Mathiassen L (2004) Successful process implementation. IEEE Softw 21(4):36-44
13. Carmel E, Agarwal R (2001) Tactical approaches for alleviating distance in global software development. IEEE Softw 18:22-29
14. Cockburn A (2004) Crystal clear, a human-powered methodology for small teams. Addison-Wesley, Boston, MA
15. Cohn M, Ford D (2003) Introducing an agile process to an organization. IEEE Comput Soc 36(6):74-78
16. Coram M, Bohner S (2005) The impact of agile methods on software project management. In: 12th International conference and Workshops on the Engineering of Computer-based Systems, Maryland, USA
17. Crowston K, Kammerer E (1998) Coordination and collective mind in software requirements development IBM. Syst J 37(2):227-245
18. Crowston K, Rybleske J, Howison J (2004) Coordination Theory. Draft for Human-Computer Interaction in Management Information Systems. Available at 14.4.2008: http://crowston.syr.edu/papers/coord2004.pdf
19. Damian D, Eberlein A, Shaw ML, Gaines BR (2000) Using different communication media in requirements negotiation. IEEE Softw 17(3):28-36
20. Dingsoyr T, Hanssen GK, Dyba T, Anker G, Nygaard JO (2006) Developing software with SCRUM in a small cross-organizational project. Developing software with SCRUM in a small cross-organizational project. In: Springer, EuroSPI 2006, LNCS 4257, pp 5-15
21. Drobka J, Noftz D, Raghu R (2004) Piloting XP on four mission-critical projects. IEEE Softw 21(6):70-75
22. Eisenhardt KM (1989) Building theories from case study research. Acad Manage Rev 14(4):532-550
23. Espinosa JA, Carmel E (2003) The impact of time separation on co-ordination in global software teams: a conceptual foundation. Softw Process Improv Pract 8(4):249-266
24. Fitzgerard B, Hartnett G, Conboy K (2006) Customising agile methods to software practices at Intel Shannon. Eur J Inf Syst 15(2):197-210
25. Goles T, Chin WW (2005) Information systems outsourcing relationships factors: detailed conceptualization and initial evidence. Data Base Adv Inf Syst 36(4):47-62
26. Grenning J (2001) Launching XP at a process-intensive company. IEEE Softw 18(6):3-9
27. Harbring C (2006) The effect on communication in incentive systems: an experimental study. Manag Decis Econ 27(5):333-353
28. Henttonen K, Blomqvist K (2005) Managing distance in a global virtual team: the evolution of trust trough technology-mediated relational communication. Strateg Change 14(2):107-119
29. Herbsleb D, Mockus A (2003) An empirical study of speed and communication in globally-distributed software development. IEEE Trans Softw Eng 29(6):1-14
30. Highsmith J (2004) Agile project management, creating innovative products. Addison-Wesley, Boston, MA
31. Highsmith J, Cockburn A (2001) Agile software development: the business of innovation. Computer 34(9):120-122
32. Holström H, Fitzgerald B, Agerfalk PJ, Conchuir EO (2006) Agile practices reduce distance in global software development. Inf Syst Manage 23(3):7-18
33. Karlström D, Runeson P (2006) Integrating agile software development into stage-gate managed product development. Empir Softw Eng 11(2):203-225
34. Klein H, Myers M (1999) A set of principles for conducting and evaluating interpretive field studies in information systems. MIS Quarterly 23(3):67-94
35. Korkala M, Abrahamson P, Kyllönen P (2006) A case study on the impact of customer communication on defects in agile software development. In: Agile 2006, Minneapolis, pp 76-88
36. Kraut R, Streeter L (1995) Coordination in software development. Commun ACM 38(3):69-79
37. Layman L, Williams L, Damian D, Bures H (2006a) Essential communication practices for extreme programming in a global software development team. Inf Softw Technol 48(9):781-794
38. Layman L, Williams L, Cunningham L (2006b) Motivations and measurements in an agile case study. J Syst Archit 52(11):654-667
39. Leon G (1995) On the diffusion of software technologies: technological frameworks and adoption profiles. In: Proceedings of The Diffusion and Adoption of Information Technology, Oslo, pp 97-116
40. Lindvall M, Muthig D, Dagnino A, Walling C, Stupperich M, Kiefer D (2004) Agile software development in large organizations. Computer 37(12):26-34
41. Lippert M, Becker-Pechau P, Breitling H, Koch J, Kornstadt A, Roock S, Schmolitzky A, Wolf H, Zullighoven H (2003) Developing complex projects using XP with extensions. Computer 36(6):1-7
42. Lycett M, Macredie R, Pateil C, Paulk R (2003) Migrating agile methods to standardized development practice. IEEE Comput Soc 36(6):79-85
43. Mann C, Maurer F (2005) A case study on the impact of SCRUM on overtime and customer satisfaction. Agile, Denver
44. Malone T, Crowston K (1994) The interdisciplinary study of coordination. ACM Comput Surv 26(1):87-119
45. Miles M, Huberman A (1999) Qualitative data analysis. Sage, London
46. Murru O, Deias R, Mugheddu G (2003) Assessing XP at a European Internet Company. IEEE Softw 20(3):37-43
47. Paasivaara M, Lassenius G (2003) Collaboration in inter-organizational software development. Softw Process Improv Pract 8(4):183-199
48. Parnas DL, Clements PC (1986) A rational design process: how and why to fake it. IEEE Trans Eng Manage 12(2):251-256
49. Pikkarainen M, Mäntyniemi A (2006) An approach for using CMMI in agile software development assessments: experiences of three case studies. Spice, Luxenburg
50. Pikkarainen M, Wang X, Conboy C (2007) Agile practices in use an innovation assimilation perspective: a multiple case study. ICIS, Montreal
51. Rasmusson J (2003) Introducing XP into greenfield projects: lessons learned. IEEE Softw 20(3):21-28
52. Rising L, Janoff NS (2000) The SCRUM software development process for small teams. IEEE Softw 17(4):26-32
53. Salo O, Abrahamsson P (2006) An iterative improvement process for agile development. Softw Process Improv Pract 12(1):81-100
54. Schwaber K, Beedle M (2002) Agile software development with SCRUM. Prentice-Hall, Upper Saddle River, NJ
55. Shukla A, Williams L (2002) Adapting extreme programming for a core software engineering course. In: Software Engineering Education and Training (CSEET'02), Kentucky, USA
56. Smite D (2006) Global software development projects in one of the biggest companies in Latvia: is geographical distribution an problem? Softw Process Improv Pract 11(1):61-76
57. Stelzer D, Mellis W (1998) Success factors of organizational change in software process improvement. Softw Process Improv Pract 4(4):227-250
58. Sutherland J (2001) Agile can scale: inventing and reinventing SCRUM in five companies. Cutter IT J 14(12):5-11
59. Svensson H, Höst M (2005) Views from an organization on how agile development affects its collaboration with a software development team. In: Proceedings of Product Focused Software Process Improvement, Lecture Notes in Computer Science. PROFES 2005, 487-501. Oulu, Finland
60. Turner R (2003) People factors in software management: lessons from comparing agile and plan-driven methods. J Def Softw Eng 22(4):4-8
61. Vriens C (2003) Certifying for CMM Level 2 and ISO9001 with XP@SCRUM. In; Agile 2003, Salt Lake City, UT
62. Weick K (1995) What theory is not, theorising is. Adm Sci Q 40(1):385-390
63. Williams L, Cockburn A (2003) Agile software development: it's about feedback and change. Computer 36(6):39-42
64. Yin RK (1994) Case study research design and methods, 3rd edn. Sage, Newbury Park, CA
65. Yin RK (2003) Case study research: design and methods, Saga, Thousand Oaks, CA