6 Principles
Agile Architecture Work
Shape it Together
Agile methods and DevOps have fundamentally changed the way software is developed today:
This applies in particular to architecture work within agile teams. Against the traditional approach — often centred on a single person in a prominent role — Continuous Architecture offers a toolset based on teamwork and a continuous flow of value in small increments.
… instead of just delivering solutions for a project
Developing products is more efficient than developing one-off solutions for individual projects. Product development means the team is guided by the needs of the users.
… instead of functional requirements.
Quality attribute requirements are the essential architecture drivers.
… until they are absolutely necessary!
Architectures are designed based on facts, not assumptions. Developing and implementing solutions that may never be used is a waste of time and resources.
Stay adaptable with small building blocks!
Large, monolithic, tightly coupled components are hard to change. Small, loosely coupled building blocks are easier to replace.
Development, testing, deployment and operations.
Architecture must consider the entire lifecycle rather than focusing solely on creating individual building blocks. Continuous Delivery must be supported by the architecture as effectively as possible.
… that reflect the design of the system being built!
The way teams are organised determines the architecture and design of the systems they work on.
Contact
