As we have demonstrated in this document, architecture models expressed in the ArchiMate language can play various useful and important roles in an Agile context. We see three main types of use:

  • Expressing the business intent, to help prioritize epics and features, and to convey the architecture vision to Agile teams

  • Fostering enterprise agility, complexity reduction, and managing architectural and technical debt

  • Facilitating the communication within, between, and across Agile teams to support collaboration and alignment

We did not discuss in detail how ArchiMate models could be used outside and beyond an IT-oriented scope, but its concepts also support the wider business world and modeling physical technology. Using Agile ways of creating and evolving non-IT results fits equally well with the use of such models.

The work set out in this document is part of a broader set of initiatives within The Open Group ArchiMate and Architecture Forums, focused on the relationships between Agile and architecture. The O-AA Standard [1] is another result of these activities, as are various white papers and guides on the topic. For more information, please visit The Open Group Library.

If you are interested in using ArchiMate models in an Agile context and are looking for tool support, please check the ArchiMate tool certification register: