How Much Up-Front? A Grounded theory of Agile Architecture
Authors:
- Michael WatermanMWMichael Waterman
- James NobleJNJames Noble
- George AllanGAGeorge Allan
- 1 May 2015
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- Vol. 1 (02705257) , 347-357
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.Keywords
This publication has 26 references indexed in Scilit:
- Traversing the Twin PeaksIEEE Software, 2013
- The Twin Peaks of Requirements and ArchitectureIEEE Software, 2013
- Complexity Made SimpleProceedings of the Canadian Engineering Education Association (CEEA), 2012
- How Much Architecture? Reducing the Up-Front Effort2012
- Agility from First Principles: Reconstructing the Concept of Agility in Information Systems DevelopmentInformation Systems Research, 2009
- Architectural Organizational PatternsIEEE Software, 2008
- What Lessons Can the Agile Community Learn from A Maverick Fighter Pilot?2006
- The Past, Present, and Future for Software ArchitectureIEEE Software, 2006
- Using risk to balance agile and plan- driven methodsComputer, 2003
- Programs, life cycles, and laws of software evolutionProceedings of the IEEE, 1980