The Enterprise Architecture function sits in the Project Management Office (PMO) in the Client Services group within Information Systems and Technology (IST), at the University of Waterloo. The EA focus is within the work and context of IST.
The EA interacts with all groups, teams, and SME at various levels within IST and other departments and business units across campus. EA is led by the Strategic Architect who works collaboratively with various stakeholders to develop and document enterprise architecture.
Maher Shinouda, Strategic Architect
Our definition of EA is “Enterprise Architecture (EA) is the digital representation of the business and information technology landscape across the enterprise classified and organized in relation to one another.”
The EA produces a set of architectural artifacts, such as diagrams, views, models, roadmaps, and sometimes stored and presented in a centralized EA repository.
The EA practice contribute to strategy and planning activities, provide insights, identify improvement opportunities, and support decision-making
To develop a set of architectural assets to improve planning and decision-making, support programs and projects activities, and enhance agility.
We have used the Enterprise Architecture Maturity Model (EAMM) to explore EA practice levels of maturity at Waterloo. We have done some review of our current state EA practice in an effort to determine where we are on the maturity curve and how can we grow further. We have identified challenges that we have been encountering since we started, determined key success factors to help us move forward, and identified opportunities where we can get involved to mature our EA practice.
Management: How are you managing the EA practice to direct resources toward the areas of scope you have defined for yourself? How could you improve?
A. Scope Definition
C. Impact Assessment
EA Maturity levels at Waterloo
EA is not yet fully scoped to form a practice and the scope of EA activities is limited. Currently the scope of EA practice has been focusing on Application, Technology, and Security architecture within the IST department, a central IT unit at the University of Waterloo, it is still at the formed level.
Current state of scope:
Engagement attributes describes how EA practice engages stakeholders based on its scope. Currently, EA engagement is being building in various areas within the IST and we are getting involved in few key projects, it is at the initiating level.
Current state of Engagement:
The impact attributes describes how the EA practice measures its performance within its scope. Currently, EA has little or no impact yet and is at the initiating level.
Current state of Impact:
Matrix and counts to measure EA work:
The Delivery attributes describes the means by which the EA practice delivers value. Currently we are at the early stage of the formed level.
Current state of Delivery:
We have identified potential means for EA practice to deliver value such as:
Currently, EA delivery attribute is considered to be in the early stage of the formed level
Our EA practice is taking practical steps to manage itself and is considered to be at the early stages of the defined level.
Current state of Management:
These are some of the challenges that we have been encountering
Powered by a free Atlassian Confluence Community License granted to Internet2. Evaluate Confluence today.