Architecture and Agility: A Shared Skillset!
Introduction
At first glance, agility and architecture appear to be worlds apart. Agility thrives on embracing change and focusing on business value during the whole development process, while architecture deals with technical decisions and system structures. However, these disciplines share surprising parallels. Both require robust collaboration, adaptability, and a shared focus on people as the cornerstone of success.
This essay explores how architecture and agility converge, focusing on four key theses:
1. Architecture is the implementation of agility.
2. Both disciplines revolve around people.
3. Agility applies across all engineering disciplines.
4. Both require navigating uncertainty.
By examining these themes, we reveal a unified approach that bridges the gap between software development practices.
Thesis 1: Architecture Is the Implementation of Agility
Agility champions adaptability through iterative cycles and reprioritization. Similarly, architecture embodies these principles by making critical decisions based on current knowledge and revising them as needed. A good example are Architecture Decision Record (ADR): They are not just used to document an architecture decisions but also the reasons that led to the decision. That way the decision can be revisited once new facts surface. So architecture embraces change - just like agility.
Reprioritizing a backlog or new stories might be the cause for revisiting architectural choices. Then architecture is driven by the results of the agile process. Because of that both activities - architecture and agility - require flexibility, transparency, and openness to change. Thus, architecture is not static but evolves with the system’s needs, mirroring agile methodologies.
Thesis 2: Both Disciplines Revolve Around People
Although agility emphasizes delivering business value and architecture appears rooted in technical systems, both are fundamentally about people. No one person can fully understand a software system or all technologies. So effective architecture relies on gathering collective expertise and fostering shared understanding.
Agility needs a similar open communication about business goals and requirements. Different stakeholders might have different ideas about what should be implemented next. Feedback from customers and other roles must be taken into account. So architecture work as well as agility means lot of communication. And effective communication requires trust.
But there are also other people challenges. For instance, successful delegation — whether assigning tasks in an agile sprint or distributing architectural responsibilities — depends on empowering teams. A mindset of mutual trust enables individuals to adapt and innovate, ensuring better outcomes.
In architecture, delegation is necessary because software systems are complex and everyone is an expert on some part of the system or some technology. So a decision should be made by the expert in the relevant field - and chances are that these are different people for different fields.
In agility, the main goal of daily stand-ups is very similar: coordinating and understanding who works on what with the goal to figure out how each person and activity can be supported best.
Military concepts like mission command ("Auftragstaktik") exemplify this principle. Leaders delegate decisions, providing flexibility without micromanagement. This approach resonates with both agility and architecture, reinforcing the human-centric nature of these disciplines. It also means that these concepts are shared much beyond software development.
Thesis 3: Agility Applies Across All Engineering Disciplines
While agility originated in software development, its principles extend to other engineering fields. At the end of the day, all engineering works in iteration. For example, automotive design involves iterative prototyping, as seen in projects like the Porsche 959. You can see some prototypes of it in the Porsche museum in Stuttgart - a modified 911 with lots of additional wood and plastic. This mirrors the iterative cycles of agile development where you would also create the product step-by-step. Building in iterations is common in all kinds of engineering. Hillel Wayne made an excellent point that iterations are not just present in software engineering but also in different engineering disciplines. They are just less frequent and more expensive.
Software architecture is no different: Some software architecture is implemented in the system but due to constant changes it evolves in iterations - just as you would expect from engineering disciplines.
So software architecture implements agility. Working in iterations and revising decisions — whether car designs or ADRs — is commonplace. Agility, therefore, is not confined to software but describes a broader framework applicable across disciplines.
Thesis 4: Both Require Navigating Uncertainty
Agility and architecture both involve making decisions with incomplete information. Agility means prioritizing backlog items based on vague customer feedback or ever changing business plans. Architecture is
selecting a technology stack without thorough experience. So uncertainty is unavoidable. The solution is not seeking false certainty through excessive planning - which is pointless due to constant change. More planning can only create an illusion of control. So both disciplines should thrive for flexibility and continuous learning.
Embracing uncertainty allows teams to make informed decisions that align with their current understanding and preferences. But at the same time they are well aware that the decisions can and probably will be revised sooner or later.
Conclusion
Architecture and agility share a core skillset grounded in collaboration, adaptability, and human-centric approaches. Whether refining a backlog or revising an ADR, success in both disciplines relies on navigating uncertainty, fostering trust, and embracing change.
By understanding these shared principles, teams can build resilient, sustainable systems that adapt to evolving needs. Ultimately, architecture and agility are not separate domains but complementary practices that together empower engineering excellence.