How Much Up-Front? A Grounded theory of Agile Architecture

Abstract

The tension between software architecture and agility is not well understood by agile practitioners or researchers. If an agile software team spends too little time designing architecture up-front then the team faces increased risk and higher chance of failure; if the team spends too much time the delivery of value to the customer is delayed, and responding to change can become extremely difficult. This paper presents a grounded theory of agile architecture that describes how agile software teams answer the question of how much upfront architecture design effort is enough. This theory, based on grounded theory research involving 44 participants, presents six forces that affect the team's context and five strategies that teams use to help them determine how much effort they should put into up-front design.

The EnviDat Concept for an Institutional Environmental Data Portal

“…Finally, as the EnviDat development workflow will gradually shift to Agile software development principles (Beck et al, 2001), this change will impact the EnviDat System Architecture. Consequently, a continuous architectural redesign of the EnviDat system architecture is necessary in order to support the proper application of the Continuous Delivery (Beck et al, 2001) concept through an agile architecture that, according to (Waterman et al, 2015) "is being able to be easily modified in response to changing requirements, is tolerant of change, and is incrementally and iteratively designed -the product of an agile development process".…”

How to Support Customisation on SaaS: A Grounded Theory from Customisation Consultants

“…A close work is Rothenberger and Srite's investigation, combining grounded theory and case studies, on the factors that influence the degree of customisation on ERP systems [5]. More generally, researchers used the grounded theory method to investigate how an agile development team control the quality [6], how much architecting is proper for different agile teams [7], etc. More approaches can be found in a survey by Stol et al [3].…”

Disseminating architectural knowledge on open-source projects

“…Several studies have also looked at social factors that influence architecture. For example, Waterman et al [57] interviewed agile software developers to determine how much architectural design to conduct "up-front" as opposed to allowing it to emerge during development. The authors identified five different strategies-respond to change, address risk, emergent architecture, big design up-front, frameworks and template architectures-that can help an agile developer make this decision.…”