In the first part of this blog post, we discussed in general how the structure of the ArchiMate modeling language matches the structure of both component and feature teams. In this second part, we want to go a bit deeper into this topic.
In my previous blog post on using the ArchiMate modeling language together with the Scaled Agile Framework (SAFe), I briefly mentioned the need for modeling the intent of the enterprise. In an agile context, this notion of intent and intentional architecture is quite important. In this blog, I want to explore that further.
It seems like an unlikely pair, doesn’t it – Agile and Enterprise Architecture? Yet, as Agile awakens to the reality of having to move fast but in concert with other parts of the organization, and EA itself becomes more engaging and business goals-oriented, it actually makes a lot of sense to want to combine the two. Both practices bring significant benefits to an organization. Together they promise to unlock efficiencies that would increase business performance to a whole new level. Who could say no to a mix of organizational agility and solid strategic decision making? That would boost any business or digital initiative.