Home
My company just released our Architecture Leader of five years and is reorganizing into a leader of Platforms and Solutions that contains platform PODs, EA POD, and Solutions POD. Currently EA consists of Data, Enterprise, and Business Architects. We are adding Solution Architects to the mix with this change. My concern is primarily on the Solution side during planning and into build as we already navigated the business architecture approach with business and product management. I’d like to know how are your organizations structured and what role partnerships have in making you successful? How do your teams work together and what services are you bringing to bear across the Strategy, Plan, Build, and Run phases?

My company just released our Architecture Leader of five years and is reorganizing into a leader of Platforms and Solutions that contains platform PODs, EA POD, and Solutions POD. Currently EA consists of Data, Enterprise, and Business Architects. We are adding Solution Architects to the mix with this change. My concern is primarily on the Solution side during planning and into build as we already navigated the business architecture approach with business and product management. I’d like to know how are your organizations structured and what role partnerships have in making you successful? How do your teams work together and what services are you bringing to bear across the Strategy, Plan, Build, and Run phases?

Process Management Team & Organizational Design Business Relationships+3 more

2.2k views1 Upvote4 Comments

Sort By:

Oldest

CIO in Governmenta year ago

Your not implies separate groups. At the Virginia Dept of Social Services, we are shifting to Product Teams that are joint, multifunctional teams focused on the line of business, no the systems. These small teams of 8-12 staff, include business reps, architects, BAs, Developers, System Admins, Security, and PMs. A centralized architecture group handles Data, Network, Application, and Security Architecture. These architects are led by a Chief Enterprise Architect who "owns" the enterprise architecture

1 2 Replies

Director of Designa year ago

Thanks for answering what I'm sure is a confusing and difficult question.

What you have described is similar to how we function. A centralized Architecture POD with a leader who is responsible for the EA practice as a whole with COE and Guilds.

Within this EA team are architects that are pulled into efforts based on strategic and architectural significance.

A couple of clarifying questions:
- are your architects statically assigned to service lines, domains, teams or are they flexible moving in and out of teams as needs arise?
- is there any delineation between your EA practice by skillset, such as Business, Enterprise, Solution or Data Architecture?

CIO in Governmenta year ago

We are establishing two levels of architects. Junior architects at the Product Team level, and senior architects at the enterprise level. We seek to have the senior architects focus on specific domains: Network, Data, Application, Security. These four senior architects led by one Chief Enterprise Architect.

Please join or sign in to view more content.

By joining the Peer Community, you'll get:

Peer Discussions and Polls
One-Minute Insights
Connect with like-minded individuals

VP of IT7 months ago

We shifted from a project to a IT Product oriented organisation to support our business lines (Domains) to improve accountability and speed of delivering business features. In addition we created a "Shared IT Product" / Platform Engineering domain who provides centralized developed and operated IT services (network, IAM, public cloud, SAP Cloud, etc) - this team provides self-services for their platforms and co-creation services to ensure that the platforms are adopted within the product teams in a seamless and efficient manner.

We setup a Chapter Enterprise Architecture which is also responsible for Solution Architecture and Systems Engineering methodology. The members of this chapter are all IT architects and solution designers/developers from the product teams - following the Community of Practice approach).
The Chapter Lead EA is similar to the Chief Enterprise Architect role and accountable for IT Governance for EA and EA practice / Solution Design methodologies. We moved from a centralized SA team to a decentralized model with product architects - one archtiect can be responsible for up to 3 products.