TOGAF: ADM Migration Planning

From Glitchdata
Jump to navigation Jump to search
ACTIVE PROCESS
  • ADM Phase F


Objectives

Togaf adm migration planning.gif

Objectives of Phase F: Migration Planning are:

  • 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 Architectures is understood by key stakeholders

Approach

The focus of Phase F is the creation of an Implementation and Migration Plan in co-operation with the portfolio and project managers.

Phase E provides an incomplete Architecture Roadmap and Implementation and Migration Plan that address the Request for Architecture Work. In Phase F this Roadmap and the Implementation and Migration Plan are integrated with the enterprise's other change activity.

Activities include assessing the dependencies, costs, and benefits of the various migration projects within the context of the enterprise's other activity. The Architecture Roadmap, Version 0.1 and Implementation and Migration Plan, Version 0.1 from Phase E will form the basis of the final Implementation and Migration Plan that will include portfolio and project-level detail.

The architecture development cycle should then be completed and lessons learned documented to enable continuous process improvement.


Inputs

Inputs to Migration Planning:

Steps

Steps to Migration Planning:

  1. Confirm Management framework interactions withe the Implementation and Migration Plan
    • The 4 management frameworks are:
      • Business Planning that conceives, directs, and provides the resources for all of the activities required to achieve concrete business objectives/outcomes.
      • Enterprise Architecture that structures and gives context to all enterprise activities delivering concrete business outcomes primarily but not exclusively in the IT domain.
      • Portfolio/Project Management that co-ordinates, designs, and builds the business systems that deliver the concrete business outcomes.
      • Operations Management that integrates, operates, and maintains the deliverables that deliver the concrete business outcomes.
  2. Assign a business value to each project
    • There are several issues to address in this activity:
      • Performance Evaluation Criteria are used by portfolio and capability managers to approve and monitor the progress of the architecture transformation.
      • Return-on-Investment Criteria have to be detailed and signed off by the various executive stakeholders.
      • Business Value has to be defined as well as techniques, such as the value chain, which are to be used to illustrate the role in achieving tangible business outcomes. Business value will be used by portfolio and capability managers to allocate resources and, in cases where there are cutbacks, business value in conjunction with return on investment can be used to determine whether an endeavor proceeds, is delayed, or is canceled.
      • Critical Success Factors (CSFs) should be established to define success for a project and/or project increment. These will provide managers and implementers with a gauge as to what constitutes a successful implementation.
      • Measures of Effectiveness (MOE) are often performance criteria and many corporations include them in the CSFs. Where they are treated discretely, it should be clear as to how these criteria are to be grouped.
      • Strategic Fit based upon the overall enterprise architecture (all tiers) will be the critical factor for allowing the approval of any new project or initiative and for determining the value of any deliverable.
  3. Estimate resource requirements, project timings, and availability/delivery vehicle
  4. Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation
  5. Confirm Transition Architecture increments/phases and update Architecture Definition Document
  6. Generate the Architecture Implementation Roadmap (time-lined) and Migration Plan
  7. Establish the architecture evolution cycle and document lessons learned.

Outputs

Outputs to Migration Planning:

  • Implementation and Migration Plan (detailed)
  • Finalized Architecture Definition Document
  • Finalized Architecture Requirements Specification
  • Finalized Architecture Roadmap
  • Transition Architecture
  • Re-Usable Architecture Building Blocks (ABBs)
  • Requests for Architecture Work (for sub-projects)
  • Architecture Contracts for implementation projects
  • Implementation Governance Model
  • Change Request arising from lessons learned


Related ADM Phases