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

@article{Waterman2015HowMU,
  title={How Much Up-Front? A Grounded theory of Agile Architecture},
  author={Michael Waterman and James Noble and G. Allan},
  journal={2015 IEEE/ACM 37th IEEE International Conference on Software Engineering},
  year={2015},
  volume={1},
  pages={347-357}
}
  • M. Waterman, J. Noble, G. Allan
  • Published 16 May 2015
  • Computer Science
  • 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering
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… 

Figures and Tables from this paper

Agility, Risk, and Uncertainty, Part 1: Designing an Agile Architecture
TLDR
Findings of recent research based on the experiences of 44 agile practitioners are discussed, to help shed light on the problem of determining how much effort goes into architecting up front, before development starts.
Balancing between stability and change in Agile teams
TLDR
A substantive theory was presented of continuously balancing between stability and change in Agile teams and three guidelines that can help organizations about to change their way of working to Agile were proposed.
Living Boundary Objects to Support Agile Inter-Team Coordination at Scale
TLDR
This thesis coined the concept of living boundary objects to manage knowledge for inter-team coordination in large-scale agile development, which helps to establish knowledge management practices that are considered beneficial by practitioners and focus on the crucial aspects to align agile teams on.
Agile architecture in the digital era: Trends and practices
TLDR
It is necessary to study the genesis of Agile architecture, as a special approach in software development, to identify current trends and practices that are adapted to the contemporary digital environment (scalability, distribution, complexity).
Goals and challenges in hybrid software development approaches
TLDR
A systematic mapping study is conducted to gather and analyze the goals and challenges in hybrid development approaches and presents the influence factors that cause conflicts in hybrid approaches and discusses how these conflicts can be addressed.
On Interfaces to Support Agile Architecting in Automotive: An Exploratory Case Study
TLDR
An exploratory case study with an automotive OEM is presented to identify characteristics of different interfaces, from non-critical interfaces that can be changed frequently and quickly, to those that are critical and require more stability and a rigorous change process.
Agile Architecture Frameworks: Challenges and Open Issues
TLDR
The challenges and open issues for the agile architecture frameworks, various frameworks such as Agile Architecture Framework (AAF) and distributed agile or adaptive development (DAD) are explored.
Real World Scrum A Grounded Theory of Variations in Practice
TLDR
Critically, it is claimed that not all variations are process misuse/abuse and proposed a nuanced classification approach to understanding variations as standard, necessary, contextual, and clear deviations for successful Scrum use and adaptation.
Reference architectures and Scrum: friends or foes?
TLDR
It is found that reference architectures can support good practice in Scrum: They provide enough design upfront without too much effort, reduce documentation activities, facilitate knowledge sharing, and contribute to "architectural thinking" of developers.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 67 REFERENCES
Reconciling agility and architecture: a theory of agile architecture
TLDR
The thesis presents a theory that describes how agile software teams design an agile architecture with reduced up-front design and which is able to respond to change, helping teams find a balance between architecture and agility.
The Effect of Complexity and Value on Architecture Planning in Agile Software Development
TLDR
Grounded Theory research into how much architecture agile teams design up-front has identified system complexity as an important factor in determining how much planning a team does up- front, while system size, although related to complexity, has a much less direct impact.
The Social Nature of Agile Teams
TLDR
An understanding of how social identity and collective effort are supported by agile methods is supported.
How Much Architecture? Reducing the Up-Front Effort
TLDR
Early results show that the experience of the architects and predefined or template architectures both help to reduce the architectural effort required without sacrificing the benefits of a full architecture design.
Agility and Architecture: Can They Coexist?
TLDR
This article talks about software architecture being relevant to the basis of aspects such as communication among team members, inputs to subsequent design decisions, documenting design assumptions, and evaluating design alternatives.
What lessons can the agile community learn from a maverick fighter pilot?
TLDR
The US Air Force Colonel John Boyd, the OODA loop, the factors which influence OodA loop speed and the possible research opportunities into software engineering culture are introduced.
What Does Research Say about Agile and Architecture?
TLDR
There is a lack of scientific support for many of the claims that are concerned with agile and architecture, and more empirical studies are needed to fully reveal the benefits and drawbacks implied by an agile software development method.
Agile Undercover: When Customers Don't Collaborate
TLDR
The causes and consequences of lack of customer involvement on Agile projects are presented and the Agile Undercover strategies used to overcome them are described.
Understanding the Importance of Trust in Distributed Agile Projects: A Practical Perspective
TLDR
It is argued that trust is one of the key factors in determining the success or failure of distributed Agile projects, and how trust can be generated and sustained by increasing effective communication and understanding cultural differences is described.
Using Risk to Balance Agile and Plan-Driven Methods
TLDR
The authors present a risk-based approach for structuring projects to incorporate both agile and plan-driven approaches in proportion to a project's needs.
...
1
2
3
4
5
...