Does this mean Architecture should not be done at the Enterprise any more?
Dont we wish that could be true. That the tech developed in one group would integrate naturally with another. The data would perfectly interface. The security worked seamlessly. The protocols were hidden. Redunandancies and sunsets were robotically self-realized. OK, the last was too much tongue in cheek. But, no, systems must interface and be interoperable, accessible, and all the other architecture “ility” words.
So EA policy was constructed made for internal systems and local data centers. Now we are in utility hardware running software for the untrained user or trained user with very little time alotted. This is just a natural program as noted in IT Footprint Progression in the Federal Government… and the role of Architecture
All that being said, losing architecture is a reality in the planning. Disruptions are moving too fast. The best way we have found is making sure the agile development efforts are build on solids plans (per the above) and make sure the architecture principles, component selection is guided by an excellent architecture runway – either via governance or an enterprise agile framework.
We have more adopted a three-pronged approach
- Strategically building collaborative relationships with our clients using Smart Lean Government concepts of building communities, integrating life events across organization types, and working towards a standing Service Integration Model
- Tactically, doing the Step 4 work products when needed
- Timing the tactical work products by implementing Agile with Architecture in concepts driven by Scaled Agile Framework