Why Agile Architecture Modeling?
From intent to solution: modeling the why, what, and how
Using models to support communication & collaboration
Creating Models in an Agile way
There is no single, ‘right’ level of detail
Take a risk-based approach: add more detail where risks are higher e.g., expensive new systems, business-critical operations, sensitive personal data, etc.
Approach this iteratively: gradually add detail as and when you need it
Value of architecture models in an Agile context:
Express the business intent, to help prioritize epics and features, and convey the vision to Agile teams
Foster enterprise agility, complexity reduction, and managing architectural and technical debt
Facilitate communication within and between Agile teams to support collaboration and alignment
Marc Lankhorst is Managing Consultant and Chief Technology Evangelist at BiZZdesign. He is responsible for BiZZdesign's vision, market development, consulting and coaching on digital business design and enterprise architecture, and for spreading the word onthe ArchiMate® language for enterprise architecture modeling, The Open Group standard of which he has managed the development.His expertise and interests range from enterprise and business architecture to service orientation, agile methods and digital business design.Marc has co-authored several books and numerous other publications, most notably ‘Enterprise Architecture at Work’, the original book on the ArchiMate language.