TOGAF ADM<\/a> separates the Phase F Implementation Plan from the Phase E Architecture Roadmap to support the transition from developing an architecture to developing the means to change. Enterprise architects have a critical role in change. However, the profession is designed for advisory, not action. We embed this best practice in the design of the architecture development method<\/a>. The enterprise architecture identified the most effective change and provided stakeholder’s the means to govern change<\/a>. They are ready to develop the implementation plan.<\/p>\n\t\t\t\n\t\t\t\t\t\t\tExplore TOGAF Certification Training\n\t\t\t<\/a>\n\t At a Glance:<\/p>\n The TOGAF ADM sets the TOGAF Framework<\/a> apart from other enterprise architecture frameworks<\/a>. It is the only enterprise architecture framework that includes all three parts of a framework<\/a> – how to document an architecture, how to build an enterprise architecture team<\/a>, and how to develop an architecture<\/a>.<\/p>\n Each TOGAF ADM<\/a> phase explains the activities to develop knowledge. Each ADM Phase develops knowledge about part of the enterprise architecture<\/a>. The interactions between the Phases are information flows. These information flows coalesce into a few critical deliverables – one is the TOGAF ADM Phase F Implementation Plan.<\/p>\n TOGAF Phase F provides the steps and information inputs for enterprise architects to support planners in crafting an Implementation Plan. It is a clear best practice for the enterprise architects to support planners. Their role is to ensure the stakeholder’s decisions in the architecture are reflected in the plan. Where prior decisions are not reflected in the Implementation Plan, the enterprise architecture must be updated. Only when your enterprise commits to a change is the candidate enterprise architecture finally approved.<\/p>\n The objective of Phase F is to transition from the Architecture Roadmap<\/a> developed in TOGAF ADM Phase E<\/a> to an Implementation Plan. The architecture roadmap has already winnowed out poor change options. The Implementation Plan is how your organization intends to execute change and reach the transition states.<\/p>\n When we explain enterprise architecture, we speak about considering possible change, weighing options. All that is in the past. The Architecture roadmap points the path forward, potential transition points. It is time for the last selection.<\/p>\n Success requires:<\/p>\n While waterfall approaches do not deliver good architecture, there should be a sharp break between an Architecture Roadmap and crafting an Implementation Plan. Exploring and discarding potential change is a valuable outcome in enterprise architecture. Phase F enters a hard, practical world.<\/p>\n Portfolio planners, Program Managers, and Project Managers do not live in a world of possibilities. They live in a hard world of execution. They speak of things like the iron triangle<\/a>. They expect to learn the destination, the expected benefits, and constraints. They intend to drag everyone over the finish line.<\/p>\n While the TOGAF Standard says you will not complete the target architecture until Phase F, your architecture will only change when your organization refuses to proceed. Otherwise, architecture development is complete.<\/p>\n An Implementation Plan provides a schedule of the projects that will realize the Target Architecture. The executable projects will be grouped into managed portfolios and programs. The Implementation Strategy<\/a> states the approach to change.<\/p>\n Let’s unpack the Implementation Plan definition. First, the Implementation Plan is a schedule. It links projects in time.<\/p>\n Second, it is based on a project. We know from PMI<\/a> that every project is a set of interdependent tasks that have a common goal. Projects characteristics:<\/p>\n Third, it groups the projects into Portfolios<\/a> and Programs<\/a> for management.<\/p>\n Last, it states how change will proceed. The Implementation Strategy<\/a> will require a change be:<\/p>\n The TOGAF Standard ADM separates Phase E and Phase F, and the Architecture Roadmap from the Implementation and Migration Plan. The separation is based on best-practice planning. An architecture roadmap supports deciding your path, destination, and where decisions still have not been made. It also supports identifying where there are unresolved forks in the journey. The implementation and migration plan only support execution.<\/p>\n We can guarantee that your current roadmaps look more like Implementation Plans than Architecture Roadmaps. However, we rarely see the work broken into discrete projects, and the projects linked into Portfolio and Program for management. Usually, it is a single extensive project. Rarely is the Implementation Strategy explicit, which leads to the project trying to decide inside the project what is the best approach. They always decide on the path that is easiest for the project.<\/p>\n Real implementation plan development is done with stakeholders, resource owners, and your enterprises planners. The enterprise architect is there to highlight the expected value, dependency, and implementation strategy. We have already assessed value. You have transition architectures. This is an exercise in planning to deliver what is expected, not figure out what is reasonable.<\/p>\n\t\t\t\n\t\t\t\t\t\t\tDownload the Enterprise Architecture Governance Guide\n\t\t\t<\/a>\n\t The two central outcomes of Phase F are an implementation plan and architecture contract. This is the action part of the enterprise architecture.<\/p>\n Most valuable use of the Implementation Plan<\/p>\n An Implementation Plan will help answer the following questions:<\/p>\n An Architecture Contract will help answer the following questions:<\/p>\n An Implementation Plan is an enterprise change execution tool. It pulls together execution and marshals an organization.<\/p>\n All TOGAF ADM Phases lead you to developing the knowledge you need. The outcome of Phase F is an Implementation Plan and supporting Architecture Contract.<\/p>\nTOGAF ADM Phase F – Craft the Implementation Plan<\/h2>\n
\n
\n
\n
![\"TOGAF](\"https:\/\/conexiam.com\/wp-content\/uploads\/2022\/08\/AdobeStock_83825573-600x400.jpeg\" "\\"TOGAF")
\n\tTOGAF ADM Overview<\/h2>\n
TOGAF ADM Develops an Enterprise Architecture<\/a><\/h3>\n
What is TOGAF Phase F?<\/h2>\n
What is the Objective of TOGAF ADM Phase F?<\/h3>\n
\n
Interaction with TOGAF Phase B<\/a>, Phase C<\/a> Phase D<\/a>, and Phase E<\/a><\/h3>\n
What is an Architecture Implementation Plan?<\/h2>\n
\n
\n
Why is an Implementation Plan Different from an Architecture Roadmap?<\/h2>\n
TOGAF ADM Phase F Implementation Plan Deliverables<\/h2>\n
\n
\n
\n
Completion of Phase F Implementation Plan<\/h2>\n