International Conference on Agile Software Development

XP 2015: Agile Processes in Software Engineering and Extreme Programming pp 218-223 | Cite as

Towards Introducing Agile Architecting in Large Companies: The CAFFEA Framework

Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 212)

Abstract

To continuously deliver value both in short-term and long-term, a key goal for large product lines companies is to combine Agile Software Development with the continuous development and management of software architecture. We have conducted interviews involving several roles at 3 sites from 2 large companies employing Agile. We have identified current architect roles and gaps in the practices employed at the organizations. From such investigation, we have developed an organizational framework, CAFFEA, for Agile architecting, including roles, teams and practices.

Keywords

Agile architecture Agile software development Organizational framework Architect roles Software process improvement 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Dingsøyr, T., Nerur, S., Balijepally, V., Moe, N.B.: A decade of agile methodologies: Towards explaining agile software development. J. Syst. Softw. 85(6), 1213–1221 (2012)CrossRefGoogle Scholar
  2. 2.
    Daneva, M., van der Veen, E., Amrit, C., Ghaisas, S., Sikkel, K., Kumar, R., Ajmeri, N., Ramteerthkar, U., Wieringa, R.: Agile requirements prioritization in large-scale outsourced system projects: An empirical study. J. Syst. Softw. 86(5), 1333–1353 (2013)CrossRefGoogle Scholar
  3. 3.
    Runeson, P., Höst, M.: Guidelines for conducting and reporting case study research in software engineering. Empir. Softw. Eng. 14(2), 131–164 (2008)CrossRefGoogle Scholar
  4. 4.
    Yin, R. K.: Case Study Research: Design and Methods. SAGE (2009)Google Scholar
  5. 5.
    Kruchten, P.: What do software architects really do? J. Syst. Softw. 81(12), 2413–2416 (2008)CrossRefGoogle Scholar
  6. 6.
    Strauss, A., Corbin, J. M.: Grounded Theory in Practice. SAGE (1997)Google Scholar
  7. 7.
    Martini, A., Bosch, J., Chaudron, M.: Architecture Technical Debt: Understanding Causes and a Qualitative Model. In: 40th Euromicro Conference on Software Engineering and Advanced Applications, Verona, pp. 85–92 (2014)Google Scholar
  8. 8.
    Leffingwell, D.: Scaling Software Agility: Best Practices for Large Enterprises. Pearson Education (2007)Google Scholar

Copyright information

© Springer International Publishing Switzerland 2015

Authors and Affiliations

  1. 1.Computer Science and EngineeringChalmers University of TechnologyGöteborgSweden

Personalised recommendations