Skip to main content
Fachgebiete
Automobil + Motoren Bauwesen + Immobilien Business IT + Informatik Elektrotechnik + Elektronik Energie + Nachhaltigkeit Finance + Banking Management + Führung Marketing + Vertrieb Maschinenbau + Werkstoffe Versicherung + Risiko
DE
EN
Bücher
Zeitschriften
Themenseiten
Organisationspsychologie Projektmanagement Marketing Smart Manufacturing
Weitere Formate
Podcasts Webinare Technik Webinare Wirtschaft Kongresse Veranstaltungskalender Awards
Jetzt Einzelzugang starten
Zugang für Unternehmen
Referenzkunden
SLX-Digitalkonferenz: Zukunftswerkstatt 2024

Mehr Umsatz mit Top-Kontakten

Am 7. Mai erfahren Sie, wie Vertriebsteams Leadgenerierung, Leadnurturing und Leadstrategien effizient steuern können.
Erweiterte Suche
Anmelden
nach oben
Erschienen in:
Buchtitelbild

2016 | OriginalPaper | Buchkapitel

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

verfasst von : Matthias Galster, Samuil Angelov, Marcel Meesters, Philipp Diebold

Erschienen in: Product-Focused Software Process Improvement

Verlag: Springer International Publishing

Einloggen

Aktivieren Sie unsere intelligente Suche, um passende Fachinhalte oder Patente zu finden.

search-config
loading …

Abstract

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.

Sie haben noch keine Lizenz? Dann Informieren Sie sich jetzt über unsere Produkte:

Springer Professional "Wirtschaft+Technik"

Online-Abonnement

Mit Springer Professional "Wirtschaft+Technik" erhalten Sie Zugriff auf:

  • über 102.000 Bücher
  • über 537 Zeitschriften

aus folgenden Fachgebieten:

  • Automobil + Motoren
  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Elektrotechnik + Elektronik
  • Energie + Nachhaltigkeit
  • Finance + Banking
  • Management + Führung
  • Marketing + Vertrieb
  • Maschinenbau + Werkstoffe
  • Versicherung + Risiko

Jetzt Wissensvorsprung sichern!

Jetzt informieren

Springer Professional "Technik"

Online-Abonnement

Mit Springer Professional "Technik" erhalten Sie Zugriff auf:

  • über 67.000 Bücher
  • über 390 Zeitschriften

aus folgenden Fachgebieten:

  • Automobil + Motoren
  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Elektrotechnik + Elektronik
  • Energie + Nachhaltigkeit
  • Maschinenbau + Werkstoffe




 

Jetzt Wissensvorsprung sichern!

Jetzt informieren

Springer Professional "Wirtschaft"

Online-Abonnement

Mit Springer Professional "Wirtschaft" erhalten Sie Zugriff auf:

  • über 67.000 Bücher
  • über 340 Zeitschriften

aus folgenden Fachgebieten:

  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Finance + Banking
  • Management + Führung
  • Marketing + Vertrieb
  • Versicherung + Risiko




Jetzt Wissensvorsprung sichern!

Jetzt informieren
Fußnoten
Literatur
1.
Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley, Boston (2012)
2.
Abrahamsson, P., Babar, M.A., Kruchten, P.: Agility and architecture: can they coexist? IEEE Softw. 27, 16–22 (2010)CrossRef
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)CrossRef
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)
5.
VersionOne Inc.: 9th Annual State of Agile Survey (2015)
6.
Runeson, P., Hoest, M.: Guidelines for conducting and reporting case study research in software engineering. Empirical Softw. Eng. 14, 131–164 (2009)CrossRef
7.
Schwaber, K.: Agile Project Management with Scrum (Developer Best Practices). Microsoft Press (2004)
8.
Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall, Upper Saddle River (2002)MATH
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)CrossRef
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 CrossRef
11.
Kruchten, P.: What do software architects really do? J. Syst. Softw. 81, 2413–2416 (2008)CrossRef
12.
Brown, S.: Software Architecture for Developers. Leanpub (2012)
13.
Faber, R.: Architects as service providers. IEEE Softw. 27, 33–40 (2010)CrossRef
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)
15.
Wohlin, C., Runeson, P., Hoest, M., Ohlsson, M., Regnell, B., Wesslen, A.: Experimentation in Software Engineering. Kluwer Academic Publications, Boston (2000)CrossRefMATH
16.
Kitchenham, B., Pfleeger, S.L.: Principles of survey research - Part 5: populations and samples. ACM SIGSOFT Softw. Eng. Notes 27, 17–20 (2002)CrossRef
17.
Fowler, M.: Who needs an architect? IEEE Softw. 20, 2–4 (2003)
18.
Miles, M.B., Huberman, A.M.: Qualitative Data Analysis. Sage Publications, Thousand Oaks (1994)
19.
Krippendorff, K.: Content Analysis: An Introduction to Its Methodology. Sage Publications, Thousand Oaks (2003)
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)
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)
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 CrossRef
23.
Cohn, M.: Succeeding with Agile: Software Development Using Scrum. Addison-Wesley, Reading (2009)
24.
Beck, K.: Extreme Programming Explained. Addison-Wesley, Boston (1999)
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)
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)
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)
28.
Madison, J.: Agile architecture interactions. IEEE Softw. 27, 41–48 (2010)CrossRef
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)
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)
31.
Woods, E.: Aligning architecture work with agile teams. IEEE Softw. 32, 24–26 (2015)CrossRef
Metadaten
Titel
A Multiple Case Study on the Architect’s Role in Scrum
verfasst von
Matthias Galster
Samuil Angelov
Marcel Meesters
Philipp Diebold
Copyright-Jahr
2016
Buch
Product-Focused Software Process Improvement

Print ISBN: 978-3-319-49093-9

Electronic ISBN: 978-3-319-49094-6

Copyright-Jahr: 2016

DOI
https://doi.org/10.1007/978-3-319-49094-6_29

Premium Partner

    Bildnachweise