1 Day(s)
🎯 LEARNING OBJECTIVES
By the end of this course, you will be able to:
By the end of this lecture, you will be able to:
Understand the role of Change Management in TOGAF ADM and Enterprise Architecture.
Apply a structured architecture change request, assessment, approval, and implementation process.
Assess the business, application, data, technology, and organizational impacts of architecture changes.
Align architecture changes with business strategy, requirements, principles, and governance.
Manage stakeholder resistance, communication, and organizational adoption.
Apply ADKAR and McKinsey 7-S models to support organizational change.
Identify change-related risks, conflicts, and mitigation actions.
Understand the roles of EA, PMO, Solution Architecture, business, and executive stakeholders in managing change.
Establish post-implementation evaluation and continuous improvement mechanisms.
🧠 PREREQUISITES
Basic understanding of Strategic Management.
Understanding of Strategic Goals and Objectives.
Basic knowledge of KPIs and OKRs.
Familiarity with business models and value creation.
Basic understanding of strategy execution and performance management.
Basic analytical and problem-solving skills.
In the TOGAF Architecture Development Method (ADM), change management is crucial to ensure alignment with the enterprise's evolving needs.
Here are the key activities in ADM change management:
Documenting and validating change requests through formal channels. This includes categorizing changes based on their impact on architecture components and securing necessary approvals.
Analyzing the implications of proposed changes on the current architecture, including impacts on systems, business processes, and data. This step helps to understand dependencies and scope out potential disruptions.
Ensuring that all architecture changes align with existing requirements or modifying requirements as necessary to reflect new business needs, facilitating consistency throughout the architecture lifecycle.
Recording approved changes in the Architecture Repository, including documentation, models, and views. This ensures that all stakeholders have access to updated, accurate information.
Keeping stakeholders informed of planned changes, timelines, and benefits through structured communication channels, thereby minimizing resistance and promoting buy-in.
Validating that all changes align with the enterprise's strategic goals. This involves ensuring that any adjustments to the architecture support the overall mission and vision of the organization.
Identifying risks associated with architecture changes and developing mitigation strategies to prevent disruption to business operations or other architectural domains.
Conducting reviews and assessments to ensure that the change adheres to architecture standards, guidelines, and principles. This step includes checking for compliance with industry regulations where applicable.
Presenting changes to an Architecture Governance Board or similar body for oversight, ensuring that modifications are in line with enterprise-wide architecture policies.
Assessing the effectiveness of the change after implementation through feedback loops, performance monitoring, and lessons-learned reviews. This supports continuous improvement in the ADM process.
The Shock for the Enterprise:
We need to understand the change management process, that it will be expected within the organization, and the organization should be ready for the changes, at its different levels as following:
Shock: some resources will be shocked by the change.
Denial: Some will not accept the change.
Frustration: Some will be frustrated and make noise
Depression: Some will execute and be depressed
Experiment: Some will try, maybe to make you fail, and some to see the results
Decision: Some decide to change
Integration: Some with higher harmony with the change.
speak about the mental part of he change management
Awareness : how to build the awareness in the organization for what we are looking for, like training sessions
Desire: how to build the desire for change, by using quantitative measures, and using highly motivated teams
Knowledge : How to acquire the knowledge, training courses, certificates, and on the job training.
Ability: Monitor performance and incrementally process improvement
Reinforcement: compensated model and potential for growth
Talk about the core steps for change management:, so In order to build Key shared values, We should:
Hard S:
Shared-Values
1. Strategy: build/align the proper one
2. Structure: under pre-defined suitable structure
3. Systems: on the right systems
Soft S:
2. Skills: Build the required skills
3. Staff: for the suitable staff
6. Styles: with the right fit management styles
Chief Enterprise Architect
Enterprise Business Architect
Enterprise Date Architect
Enterprise Application Architect
Enterprise IT Architect
Enterprise Infrastructure Architect
The role of EA unit is:
1. Digital transformation strategy
2. Digital transformation
3. Enterprise architecture
As EA think globally, that may conflict with the level of freedom per each area:
1. EA AND PMO regarding the acceleration of the projects
2. EA and SA, regarding the solution architecture and perfectionism
3.EA and CFO, Regarding the cost
Enterprise Architect
Archimate
Dr. Ghoniem Lawaty
Tech Evangelist