TOGAF 9.1 Series — ADM Phase — F — Migration Planning

Have you ever heard of TOGAF and never really understood it? In my TOGAF 9.1 series of articles, I will give you summary points what TOGAF is and what you will learn in TOGAF.

I have written the TOGAF exam a while back. I thought that writing this series will let me review the TOGAF content and believe that it would be valuable to others. It is always a good practice to regularly review the contents of a topic that you have learned.

I’m not going to rewrite the official TOGAF books content in my article series. Some sections will only contain bullet points of key terms used in TOGAF. Always reference the official TOGAF book for more details.

Legal Points

TOGAF is a trademark of The Open Group. They maintain the TOGAF standard and release new versions of the framework. I highly recommend that you read the official website and content of TOGAF on the official site: http://www.opengroup.org/subjectareas/enterprise/togaf

The contents in my article series are my opinions and in no way reflects the views of The Open Group.

If you are interested in learning all the finer details of TOGAF or want to write the exam then buy the official book:

Figure 1: TOGAF Version 9.1 book

ADM Phase — F — Migration Planning

Objectives

  • Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan.
  • Ensure that the Implementation and Migration Plan is coordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio.
  • Ensure that the business value and cost of work packages and Transition Architecture is understood by key stakeholders.

Steps

  • Confirm management framework interactions for Implementation and Migration Plan.
  • Assign a business value to each work package.
  • Estimate resource requirements, project timings and availability /delivery vehicle.
  • Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation.
  • Confirm Architecture Roadmap and update Architecture Definition Document.
  • Complete the Implementation and Migration Plan
  • Complete the development cycle and document lessons learned.

Inputs

  • Request for Architecture Work

Capability Assessment, including

  • Business Capability
  • IT Capability
  • Communication Plan
  • Organizational Model for Enterprise Architecture
  • Governance models and frameworks
  • Tailored Architecture Framework
  • Statement of Architecture Work
  • Architecture Vision
  • Architecture Repository

Draft Architecture Definition Document, including

  • Transition Architecture
  • Draft Architecture Requirements Specification
  • Change Requests for existing programs and projects.
  • Architecture Roadmap

Implementation and Migration Plan, including

  • High-level Implementation and Migration Strategy

Outputs

Implementation and Migration Plan (detailed), including

  • Implementation and Migration Strategy
  • Project and portfolio breakdown of the implementation
  • Project charters (optional)

Finalized Architecture Definition Document, including

  • Finalized Transition Architectures
  • Finalized Architecture Requirements Specification
  • Finalized Architecture Roadmap
  • Re-Usable Architecture Building Blocks
  • Requests for Architecture Work for a new iteration of the ADM cycle
  • Change requests for the Architecture Capability arising from lessons learned

Originally published at cecilblog.com on March 16, 2016.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.