Abstract
Software has permeated every aspect of modern life. Human kind flew to the moon on 140,000 lines of source code and yet, when you wake up in the morning and put on your smartwatch, more than 10 million lines of code have just been strapped to your wrist. The same goes for the smartphone that happens to be buried somewhere in your bag; 12+ million lines of code in your pocket. The plane on route to your vacation destination will be hurling you and 14+ million lines of code through the air. These magnitudes are already impressing, and yet a quick ‘like’ on your favorite social network will be powered by 61+ million lines of code and the pair of socks you have just bought at the retailer of your choice will fire off data into an enterprise system consisting of more than 400 million lines of code. To put these numbers into perspective, one million lines of code printed out, would cover 18,000 pages and equals about 14 copies of War and Peace. The development of such massive and complex software involves equally substantial and complex organizations whose members need to be carefully coordinated.
Software is like entropy. It is difficult to grasp, weighs nothing, and obeys the second law of thermodynamics; i.e. it always increases.
—Norman Ralph Augustine
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
- 2.
- 3.
- 4.
War and Peace by Leo Tolstoy, first published in 1869 with 1225 pages.
References
Abrahamsson, P., Conboy, K., & Wang, X. (2009). “Lots done, more to do”: The current state of agile systems development research. European Journal of Information Systems, 18(4), 281–284. Retrieved from http://www.palgrave-journals.com/ejis/journal/v18/n4/abs/ejis200927a.html
Ågerfalk, P. J., Fitzgerald, B., & Slaughter, S. (2009). Flexible and distributed information systems development: State of the art and research challenges. Information Systems Research, 20(3), 317–328.
Begel, A., & Nagappan, N. (2007). Usage and perceptions of agile software development in an industrial context: An exploratory study. In International Symposium on Empirical Software Engineering and Measurement (pp. 255–264). IEEE Computer Society. Retrieved from http://doi.ieeecomputersociety.org/10.1109/ESEM.2007.12
Benbasat, I., Goldstein, D. K., & Mead, M. (1987). The case research strategy in studies of information systems. MIS Quarterly, 11(3).
Dingsøyr, T., & Moe, N. B. (2013). Research challenges in large-scale agile software development. ACM SIGSOFT Software Engineering Notes, 38(5), 38–39. Retrieved from http://dl.acm.org/citation.cfm?id=2507288.2507322
Dingsøyr, T., & Moe, N. B. (2014). Towards principles of large-scale agile development. In T. Dingsøyr, N. Moe, R. Tonelli, S. Counsell, C. Gencel, & K. Petersen (Eds.), Agile methods. Large-scale development, refactoring, testing, and estimation (Vol. 199, pp. 1–8). Springer International Publishing. Retrieved from http://www.springer.com/computer/swe/book/978-3-319-14357-6
Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9–10), 833–859. Retrieved from http://linkinghub.elsevier.com/retrieve/pii/S0950584908000256
Edmondson, A. C., & McManus, S. E. (2007). Methodological fit in management field research. The Academy of Management Review, 32(4), 1155–1179.
Eisenhardt, K. M. (1989). Building theories from case study research. The Academy of Management Review, 14(4), 532–550. Retrieved from http://www.jstor.org/stable/258557
Fry, C., & Greene, S. (2007). Large scale agile transformation in an on-demand world. In Proceedings of the AGILE Conference 2007 (pp. 136–142). Washington, DC.
Kirsch, L. J. (2004). Deploying common systems globally: The dynamics of control. Information Systems Research, 15(4), 374–395.
Kozlowski, S. W. J., & Bell, B. S. (2003). Work groups and teams in organizations. In W. C. Borman, D. R. Ilgen, & R. J. Klimoski (Eds.), Handbook of psychology: Industrial and organizational psychology (Vol. 12, pp. 333–375). New York: Wiley.
Larman, C., & Vodde, B. (2008). Scaling lean & agile development: Thinking and organizational tools for large-scale Scrum. Upper Saddle River, NJ: Addison-Wesley Professional.
Lyytinen, K., & Newman, M. (2006). Working papers on information systems punctuated equilibrium, process models and information system development and change : Towards a socio-technical process analysis. Sprouts: Working Papers on Information Systems, 6(2006), 1–49. Retrieved from http://sprouts.aisnet.org/46/1/060101_.pdf
Lyytinen, K., & Newman, M. (2008). Explaining information systems change: A punctuated socio-technical change model. European Journal of Information Systems, 17(6), 589–613. Retrieved from http://www.palgrave-journals.com/ejis/journal/v17/n6/abs/ejis200850a.html
Mackert, O., Hildenbrand, T., & Podbicanin, A. (2010). Vom Projekt zum Produkt - SAP’s Weg zum “Lean Software Product Development.” In Vom Projekt zum Produkt. Fachtagung des GI-Fachausschusses Management der Anwendungsentwicklung und -wartung im Fachbereich Wirtschaftsinformatik (WI-MAW), 01.-03. Dezember 2010 in Aachen (pp. 13–25).
Madill, A., Jordan, A., & Shirley, C. (2000). Objectivity and reliability in qualitative analysis: Realist, contextualist and radical constructionist epistemologies. British Journal of Psychology, 91(1), 1–20. Retrieved from http://dx.doi.org/10.1348/000712600161646
Markus, M. L., & Robey, D. (1988). Information technology and organizational change: Causal structure in theory and research. Management Science, 34(5), 583–598. Retrieved from http://www.jstor.org/stable/10.2307/2632080
Mathieu, J. E., Marks, M. A., & Zaccaro, S. J. (2001). Multiteam systems. In N. Anderson, D. S. Ones, H. K. Sinangil, & C. Viswesvaran (Eds.), Handbook of industrial, work and organizational psychology, Volume 2 Organizational psychology (Vol. 2, pp. 289–313). London: Sage Publications Ltd.
Mohr, L. B. (1982). Explaining organizational behavior. San Francisco: Jossey-Bass.
Nerur, S. P., Mahapatra, R. K., & Mangalaraj, G. (2005). Challenges of migrating to agile methodologies. Communications of the ACM, 48(5), 72–78.
Shepperd, J. a. (1993). Productivity loss in performance groups: A motivation analysis. Psychological Bulletin, 113(1), 67–81.
Van De Ven, A. H., Delbecq, A. L., & Koenig, R. J. (1976). Determinants of coordination modes within organizations. American Sociological Review, 41(2), 322–338. Retrieved from http://www.jstor.org/stable/2094477
VersionOne Inc. (2012). 7th Annual State of Agile Development Survey. Retrieved from http://www.versionone.com/pdf/7th-Annual-State-of-Agile-Development-Survey.pdf
West, D., Grant, T., Gerush, M., & D’Silva, D. (2010). Agile development: Mainstream adoption has changed agility. Forrester Research.
Yin, R. K. (2009). Case study research: Design and methods (4th ed.). Sage Publications, Inc.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2017 Springer International Publishing AG
About this chapter
Cite this chapter
Scheerer, A. (2017). Introduction. In: Coordination in Large-Scale Agile Software Development. Progress in IS. Springer, Cham. https://doi.org/10.1007/978-3-319-55327-6_1
Download citation
DOI: https://doi.org/10.1007/978-3-319-55327-6_1
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-55326-9
Online ISBN: 978-3-319-55327-6
eBook Packages: Business and ManagementBusiness and Management (R0)