1. My Summary of Gartner’s IT Score for Enterprise Architecture
Phase Initial Developing Defined Managed Optimizing
Description No formal EA program An EA program is in place, but is An EA program is in place and The EA program is This level indicates that a
is in place working poorly due to weaknesses delivering value to the business delivering value and is company has achieved a high
in several dimensions of maturity repeatable level of maturity
Stakeholders Infrastructure managers and CIO / Director of IT is more actively getting Project/Program Managers now actively Senior Corporate Management All Stakeholders actively participate in
Application developers involved and is beginning to see the value of participate. Business Unit Manager have actively engage with EA EA
Support
actively participate but EA. Project/Program Managers start to ask EA requested EA projects. Senior Corporate
CIO / Director of IT is still not for assistance. Some Business Unit Manager Management become more aware of EA
sure of the value of EA. have engaged in EA projects
Communication EA communication activities Some EA communications are planned and Most EA communications are planned and All EA communications are planned and are tailored to specific stakeholder
are ad-hoc and generic tailored to specific stakeholder needs tailored to specific stakeholder needs needs
Team Resources Some people have been For some projects, Subject matter experts Subject matter experts used on most EA Subject matter experts used on all Enterprise architects that are certified
assigned enterprise have been recruited temporarily onto the EA projects. Some Long-term EA team members projects. All EA Team Members are through an internally approved
architecture as their virtual team to participate in developing the that have received advanced EA training, some certified in EA framework. A certification scheme. Specialized EA
primary responsibility. Some EA. Most EA team members that have are certified. A specialized EA tool is used to specialized EA tool is used to tools are well integrated with other
team members that have received basic EA training. Basic tools such as document the EA document the EA with some related tools (e.g., CMDB, BPM)
received basic EA training. MS Office are used to document the EA integration to other related tools
Basic tools such as MS Office
are used to document the EA
EA Development No EA Development process At least one cycle of the EA development An EA development process has been defined or EA development cycles are The EA development process is
or EA Governance defined. process has been completed. Some adopted. A subset of EA deliverables has been planned as projects and tracked for reviewed and improved periodically
Method
Majority of Architecture Architecture development decisions are made prioritized and scheduled for development quality, schedule and cost. The EA as required. The EA may be updated
development decisions are jointly by IT and the business (i.e., duopoly) EA refreshes feed into the budget planning cycle is refreshed at least annually more frequently when out-of-cycle
made by IT An EA governance framework has been created changes occur
Process EA Team is somewhat EA is integrated with the IT change EA is integrated with IT project/program EA is integrated with the technology acquisition process. EA is integrated
isolated or informally management process and with application management and application development with business strategic planning and with business change program
Integration
integrated portfolio management methodologies take into consideration EA. management
Deliverables Creates deliverables related Creates Technical and Solution architecture Looks at Project portfolio requirements. Creates EA Deliverables shape Business Deliverables looks at Business
to Technology trends. Has a principles and standards. Uses Business Information architecture principles and strategies. Develops Business environmental trends. Future state
reactive view to Future State capability models sometimes and looks a year standards. Future State is planned on a 1-3 years architecture principles and planning 5 years or more ahead
Planning ahead when planning Future State horizon standards. Future state planning 3-
5 years ahead
Disclosure and Disclosure and Compliance is informal EA reviews are integrated into the system An appropriate appeal process has been defined for architecture review
development lifecycle (SDLC) process. Projects board Decision. EA program compliance is well-defined and clearly
Compliance
that are not compliant with EA can be stopped communicated within the enterprise. A process is in place to select projects
through the review process. The enterprise for a formal architecture review based on size, risk and/or other key factors
architecture team is aware of all projects that
are planned or underway within the organization
Metrics No Metrics Defined EA metrics have been identified to track planned EA metrics have been identified to track the impact of EA on IT and the
to actual EA deliverables. Metrics on Project business. Roadmap adoption is tracked
compliance and the number of projects requiring
EA Consulting is tracked
Stakeholders EA has a positive impact on reducing IT EA enables reuse of assets EA has a positive impact on reducing project EA has a positive impact on EA has a positive impact on enabling
service provision costs work effort and on business strategy optimizing business processes and organizational change
Perceptions
on improving information quality
and accessibility. EA enables
innovation