Abstract
Agile software development is about to become mainstream in the software industry. Its introduction requires a significant change of the mindset towards openness, honesty, and flexibility. Therefore, the adoption of agile development by the industry is also a process of cultural change that takes a long time and surfaces many issues which have been neglected or hidden with other development models. Adoption of agile practices in global companies raises consequences which are seldom anticipated. According to our observations large-scale agile software development demands a management style focusing on constant learning and communication, a certain degree of up-front planning to support agility and emergent design, and in-depth examination of software development practices that should not only be seen as rituals of predefined process models. They should rather be regarded as tools in a toolbox which all can be useful in all development phases. Also necessary is a legal framework for contracts that support agile software development.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Aranda J, Easterbrook S, Wilson G (2008) Observations on conway’s law in scientific computing. In: 1st workshop on socio-technical congruence (STC), at the 30th international conference on software engineering (ICSE’08), Leipzig, Germany, 10 May 2008. http://www.cs.toronto.edu/jaranda/pubs/Aranda08-STC-final.pdf
Beck K, Beedle M, van Bennekum A, Cockburn A, Cunningham W, Fowler M, Grenning J, Highsmith J, Hunt A, Jeffries R, Kern J, Marick B, Martin RC, Mellor S, Schwaber K, Sutherland J, Thomas D (2001) The agile manifesto. http://agilemanifesto.org/. Cited 12 Dec 2012
Boehm BW (1988) A spiral model of software development and enhancement. IEEE Comput 21(5):61–72. http://weblog.erenkrantz.com/jerenk/phase-ii/Boe88.pdf. Cited 12 Dec 2012
Conway ME (1968) How do committees invent? Datamation 14(4):28–31
DeMarco T (1997) The deadline: a novel about project management. Dorset House, New York
Janes AA, Succi G (2012) The dark side of agile software development. In: Proceedings of the ACM international symposium on new ideas, new paradigms, and reflections on programming and software, Onward! ‘12. ACM, New York, pp 215–228. doi:10.1145/2384592.2384612. http://doi.acm.org/10.1145/2384592.2384612
Kampfmann R, Heymann J (2013) SAP’s road to agile software development. In: Brunetti G, Feld T, Schnitter J, Webel C, Heuser L (eds) Future business software 2012—Proceedings of the first international FBS conference, Walldorf, Germany, 25 Sep 2012. Springer, Heidelberg
Leffingwell D (2011) Agile software requirements: lean requirements practices for teams, programs, and the enterprise, 1st edn. Addison-Wesley Professional, Reading
McCormack A, Baldwin C, Rusnack J (2012) Exploring the duality between product and organizational architectures: a test of the “mirroring” hypothesis. Res Policy 41(8):1309–1324
Nagappan N, Murphy B, Basili VR (2008) The influence of organizational structure on software quality: an empirical case study. In: Schäfer W, Dwyer MB, Gruhn V (eds) ICSE. ACM, pp 521–530
O’Brien L, Booch G (2009) Grady Booch on design patterns, OOP, and coffee. http://www.informit.com/articles/article.aspx?p=1405569. Cited 12 Dec 2012
Pichler R (2007) Scrum: Agiles Projektmanagement erfolgreich einsetzen. dpunkt, Heidelberg
Schwaber K (2004) Agile project management with Scrum. Microsoft Press, Redmond
Takeuchi H, Nonaka I (1986) The new new product development game. Harvard Business Rev 64:137–146
Tütek H, Ay C (2000) Resolving conflict between marketing and engineering: a quest for effective integration. In: First international joint symposium on business administration; challenges for business administrators in the new millennium, Çanakkale Onsekiz Mart University and Silesian University Gökçeada, pp 535–546. http://www.opf.slu.cz/vvr/akce/turecko/pdf/Tutek.pdf. Cited 12 Dec 2012
Acknowledgments
We wish to thank the following people for their contributions and fruitful discussions: Michael Backhaus, Tim Dahmen, Martin Fassunge, Behnaz Gholami, Tobias Hildenbrand, Eva Holmes, Roger Kilian-Kehr, Alexander Scheer, Christoph Schmidt, and Dirk Voelz. Part of this work has been sponsored by the German Bundesministerium für Bildung und Forschung.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this paper
Cite this paper
Schnitter, J., Geppert, J. (2014). Agile Software Development: What is Left to Do?. In: Brunetti, G., Feld, T., Heuser, L., Schnitter, J., Webel, C. (eds) Future Business Software. Progress in IS. Springer, Cham. https://doi.org/10.1007/978-3-319-04144-5_8
Download citation
DOI: https://doi.org/10.1007/978-3-319-04144-5_8
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-04143-8
Online ISBN: 978-3-319-04144-5
eBook Packages: Computer ScienceComputer Science (R0)