Welcome
Jim Phelps - welcomes everyone. Talks about Agility - both Technical and Culture - being the thing that keeps him up at night.
Once around the room with introductions and pain points.
Commonly heard things
budgets that are in silos and the project decisions that aren't aligned with the a larger strategy.
Dealing with Identity Management issues
Being focused on individual projects rather than working on the larger picture
Dealing with homegrown apps, ERPs
Federated Architecture
U Chicago has an Architecture steering group made up of senior leaders and senior technologists. They look at issues - not a roadmap group - that are in front of them.
CMU - also has Federated Architecture model.
Architectural Control via Budget Control
Discussion about having a CTO who reviews yearly budgets and eliminates funding that doesn't align with architectural plans.
Isolated Architecture
Architecture that stuck in its own silo within a single group.
Head Architect with Domain Architects
A central architect or architecture group with domain architects in each of the groups. The head architect and domain architects work together to set the enterprise architecture and to set standards in each of the areas.
Architecture as Advisory Function vs. Architecture as Control
Two types of engagement models: One is Architects act as advisers to projects - making suggestions and offering a suite of tools to projects. The second is architecture as a gate function where projects go through architectural reviews to make sure that they are aligned with the enterprise architecture. Most higher education institutions present are advisory.