A Multiple Case Study on the Architect’s Role in Scrum

  • Matthias GalsterEmail author
  • Samuil Angelov
  • Marcel Meesters
  • Philipp Diebold
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 10027)


Context: Previous research investigated how to approach architecting in agile projects (e.g., in terms of processes and practices), but the role that architects play in Scrum is still not well understood. Objective: We aim at capturing scenarios of how architects (or those taking on architecture-related tasks) are involved in Scrum. Furthermore, we aim at identifying how those taking on the role of the architect interact with other roles in Scrum. Method: We conducted a multiple case study and interviews with practitioners from six Dutch software organizations. Results: We identified three generic scenarios of architects in Scrum (“internal architect”, “external architect”, “internal and external architects”). We found that how architects interact with other roles in Scrum heavily depends on the Product Owner role. Conclusions: Some of our results are not in line with recommended practices in the Scrum Guide. Our findings support those who take on architecture-related tasks in preparing for Scrum-like projects.


Software architect Architecture Agile software development Scrum 


  1. 1.
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley, Boston (2012)Google Scholar
  2. 2.
    Abrahamsson, P., Babar, M.A., Kruchten, P.: Agility and architecture: can they coexist? IEEE Softw. 27, 16–22 (2010)CrossRefGoogle Scholar
  3. 3.
    Yang, C., Liang, P., Avgeriou, P.: A systematic mapping study on the combination of software architecture and agile development. J. Syst. Softw. 111, 157–184 (2016)CrossRefGoogle Scholar
  4. 4.
    Eloranta, V.-P., Koskimies, K.: Lightweight architecture knowledge management for agile software development. In: Babar, M.A., Brown, A., Mistrik, I. (eds.) Agile Software Architecture. Morgan Kaufmann, Boston (2014)Google Scholar
  5. 5.
    VersionOne Inc.: 9th Annual State of Agile Survey (2015)Google Scholar
  6. 6.
    Runeson, P., Hoest, M.: Guidelines for conducting and reporting case study research in software engineering. Empirical Softw. Eng. 14, 131–164 (2009)CrossRefGoogle Scholar
  7. 7.
    Schwaber, K.: Agile Project Management with Scrum (Developer Best Practices). Microsoft Press (2004)Google Scholar
  8. 8.
    Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall, Upper Saddle River (2002)zbMATHGoogle Scholar
  9. 9.
    Friedrichsen, U.: Opportunities, threats, and limitations of emergent architecture. In: Babar, M.A., Brown, A., Mistrik, I. (eds.) Agile Software Architecture, pp. 335–355. Morgan Kaufmann, Boston (2014)CrossRefGoogle Scholar
  10. 10.
    Diebold, P., Ostberg, J.-P., Wagner, S., Zendler, U.: What do practitioners vary in using scrum? In: Lassenius, C., Dingsøyr, T., Paasivaara, M. (eds.) XP 2015. LNBIP, vol. 212, pp. 40–51. Springer, Heidelberg (2015). doi: 10.1007/978-3-319-18612-2_4 CrossRefGoogle Scholar
  11. 11.
    Kruchten, P.: What do software architects really do? J. Syst. Softw. 81, 2413–2416 (2008)CrossRefGoogle Scholar
  12. 12.
    Brown, S.: Software Architecture for Developers. Leanpub (2012)Google Scholar
  13. 13.
    Faber, R.: Architects as service providers. IEEE Softw. 27, 33–40 (2010)CrossRefGoogle Scholar
  14. 14.
    Angelov, S., Meesters, M., Galster, M.: Architects in scrum: what challenges do they face? In: 10th European Conference on Software Architecture (ECSA), Copenhagen, Denmark. Springer, Switzerland (2016, in press)Google Scholar
  15. 15.
    Wohlin, C., Runeson, P., Hoest, M., Ohlsson, M., Regnell, B., Wesslen, A.: Experimentation in Software Engineering. Kluwer Academic Publications, Boston (2000)CrossRefzbMATHGoogle Scholar
  16. 16.
    Kitchenham, B., Pfleeger, S.L.: Principles of survey research - Part 5: populations and samples. ACM SIGSOFT Softw. Eng. Notes 27, 17–20 (2002)CrossRefGoogle Scholar
  17. 17.
    Fowler, M.: Who needs an architect? IEEE Softw. 20, 2–4 (2003)Google Scholar
  18. 18.
    Miles, M.B., Huberman, A.M.: Qualitative Data Analysis. Sage Publications, Thousand Oaks (1994)Google Scholar
  19. 19.
    Krippendorff, K.: Content Analysis: An Introduction to Its Methodology. Sage Publications, Thousand Oaks (2003)Google Scholar
  20. 20.
    Torchiano, M., Ricca, F.: Six reasons for rejecting an industrial survey paper. In: First International Workshop on Conducting Empirical Studies in Industry (CESI), pp. 1–6. IEEE Computer Society, San Francisco (2013)Google Scholar
  21. 21.
    Babar, M.A., Ihme, T., Pikkarainen, M.: An industrial case of exploiting product line architectures in agile software development. In: 13th International Software Product Line Conference, pp. 171–179. CMU, San Francisco (2009)Google Scholar
  22. 22.
    Rost, D., Weitzel, B., Naab, M., Lenhart, T., Schmitt, H.: Distilling best practices for agile development from architecture methodology. In: Weyns, D., Mirandola, R., Crnkovic, I. (eds.) ECSA 2015. LNCS, vol. 9278, pp. 259–267. Springer, Heidelberg (2015). doi: 10.1007/978-3-319-23727-5_21 CrossRefGoogle Scholar
  23. 23.
    Cohn, M.: Succeeding with Agile: Software Development Using Scrum. Addison-Wesley, Reading (2009)Google Scholar
  24. 24.
    Beck, K.: Extreme Programming Explained. Addison-Wesley, Boston (1999)Google Scholar
  25. 25.
    Waterman, M., Noble, J., Allan, G.: How much up-front? a grounded theory on agile architecture. In: 37th International Conference on Software Architecture, pp. 347–357. IEEE Computer Society, Florence (2015)Google Scholar
  26. 26.
    Martini, A., Bosch, J.: A multiple case study of continuous architecting in large agile companies: current gaps and the caffea framework. In: 13th Working IEEE/IFIP Conference on Software Architecture (WICSA), pp. 1–10. IEEE, Florence (2016)Google Scholar
  27. 27.
    van der Ven, J.S., Bosch, J.: Architecture decisions: who, how and when? In: Babar, M.A., Brown, A., Mistrik, I. (eds.) Agile Software Architecture, pp. 113–136. Morgan Kaufmann, Boston (2014)Google Scholar
  28. 28.
    Madison, J.: Agile architecture interactions. IEEE Softw. 27, 41–48 (2010)CrossRefGoogle Scholar
  29. 29.
    Martini, A., Pareto, L., Bosch, J.: Role of architects in agile organizations. In: Bosch, J. (ed.) Continuous Software Engineering, pp. 39–50. Springer, Berlin (2014)Google Scholar
  30. 30.
    Babar, M.A.: An exploratory study of architectural practices and challenges in using agile software development approaches. In: Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture (WICSA/ECSA), pp. 81–90. IEEE Computer Society, Cambridge (2009)Google Scholar
  31. 31.
    Woods, E.: Aligning architecture work with agile teams. IEEE Softw. 32, 24–26 (2015)CrossRefGoogle Scholar

Copyright information

© Springer International Publishing AG 2016

Authors and Affiliations

  • Matthias Galster
    • 1
    Email author
  • Samuil Angelov
    • 2
  • Marcel Meesters
    • 2
  • Philipp Diebold
    • 3
  1. 1.University of CanterburyChristchurchNew Zealand
  2. 2.Software EngineeringFontys University of Applied SciencesEindhovenThe Netherlands
  3. 3.Fraunhofer Institute for Experimental Software EngineeringKaiserslauternGermany

Personalised recommendations