Please enable JavaScript.
Coggle requires JavaScript to display documents.
ADM Module 2-3 (Part 2) (Phase F - Migration Planning (Finalize the…
ADM
Module 2-3 (Part 2)
Phase E - Opportunities and Solutions
Initial
complete
version
of the
Architecture Roadmap
, based on Gap analysis of BDAT
All Gap analyses
from B, C and D phases get
consolidated together
to reveal the Architectural road map
Determine if incremental approach required
Formulate Basic implementation and migration strategy
Identify and group work packages - e.g, 3-4 things to be done together, 2 things to be done later etc.
Gives an opportunity to break up the work packages in Incremental packages call
"Transition Architectures"
Phase F - Migration Planning
Finalize
the Architecture Roadmap
,
Implementation
and
Migration Plan
Effectively means planning project schedule, working with PMs, working with implementors, getting estimates etc.
Ensure that plan is coordinated with enterprise's approach to change
Based on Business' Approach to Change -
:red_flag:
Very Resistant to change
- too much time required for small changes, plan small work packages at a time
:red_flag:
Risk Taker
- more agile and moving things quickly, adopt a different approach
:tada:Ensure the
business value of the approach
is
understood by stakeholders
Start thinking about
implementation - costs, resources, timing
Transition
from
developing the architecture to implementing
Phase G - Implementation Governance
Ensure conformance with target architecture
Your implementation team is
"following"
the
agreed architecture.
Governance duties -
changes
during the course of implementation
are accommodated, improvised and implemented
Handling change requests
from implementation team
:tada:
Update the baseline architecture based on changes in current architecture
- E.g, transitional architecture changes, base architecture should also updated accordingly
Phase H - Architecture Change Management
Keeping
the
architecture
alive
Ensuring architecture capability is not lost - Mean architecture is still feasible for upcoming changes and updates
Ensure
Architecture Governance
is
happening
- Changes are accepted, denied, logged
Ensure the "enterprise" Architecture Capability is maintained
Monitoring : Changes
to
business
enterprise, changes to the
industry
, changes to
technology
, formal change requests
:red_flag:
Center Phase - Requirements Management
Center of the hub - center of all phases
Operates continuously
during the ADM process
Not part of any cycle - No specific timeline to start or end
Requirements change all the time
- has a process to address changes
E.g. If business has new requirement and Phase B (Business planning) has already passed, should we go back to Phase B and re-address this requirement?
More discussion needs to happen or is it a minor change that can be rolled-in without any impact?
Involves
assessing impact
of these changes
New competitor, new legislation, dis-proven assumption, new company policy