Jim Phelps, Director of Enterprise Architecture and Strategy.
I have been at UW for 3 1/2 years now.
The EA practice was started here before I was hired. A group of interested people (mostly central IT but with some campus partners) came together and established the EASG (Enterprise Architecture Steering Group). As a group, the wrote principles and did a couple of EA whitepapers. They then made the recommendation that UW-IT (the central IT group) should hire an EA.
The practice here started as a grassroots effort inside of UW-IT
We have an Enterprise Business Architect, we had an Enterprise Information Architect and we have an Enterprise Solution Architect.
Our focus is mostly on the business and solution architecture for the center IT unit. We are working on Strategy Management for UW-IT, refactoring and improving our investment/service management business processes along with solutions for shared DevOps tools and monitoring among other things.
We were 4 FTE until very recently. We are now 3 FTE located in the central IT unit. I report to an AVP who reports to the VP-IT/CIO.
We are building a federated architecture practice. We have run several courses teaching campus members things like capability mapping, business process mapping, brick diagrams. We have a Community of Practice where my team brings together 30ish people to work on topics and learn about best practices.
My vision is that we have a well linked distributed EA function where there are architects in place in various groups and domains who contribute to the overall architecture best practices, artifacts, etc. (see Spreading EA Skills Across the Organization and the CEB articles linked in the sidebar)
UW's EA practice is working towards a federated model of EA.
Business Architecture is a core practice within our EA group.
We see the needs for new skills across the organization.
We manage our work using Scrum/Agile
Our major focus has been building a Strategy Management practice