Developing the Architecture Vision

Value to your organisation of the "Developing the Architecture Vision" programme.

This first phase of the TOGAF Architecture Development Method (ADM) will prepare an organisation for a successful architecture project based on validated business requirements. It will align the IT strategy with the business goals and drivers. TOGAF best practise will help to minimise the cost of IT development through increased reuse and better utilisation of resources.

This is the initial phase of an architecture development cycle. It includes gathering information about scope, the key steps, methods, information requirements and obtaining approval for the architecture development cycle to proceed.

Objectives for the programme

• To ensure that this evolution of the architecture development cycle has proper recognition and endorsement from the corporate management of the enterprise, and the support and commitment of the necessary line management
• To define and organize an architecture development cycle within the overall context of the architecture framework, as established in the Preliminary phase (Getting Started With TOGAF)
• To validate the business principles, business goals, and strategic business drivers of the organization and the enterprise architecture Key Performance Indicators (KPIs)
• To define the scope of, and to identify and prioritize the components of, the Baseline Architecture effort
• To define the relevant stakeholders, and their concerns and objectives using the Stakeholders management techniques
• To define the key business requirements to be addressed in this architecture effort, and the constraints that must be dealt with, using Business Scenarios
• To articulate an Architecture Vision and formalize the value proposition that demonstrates a response to those requirements and constraints
• To create a comprehensive plan that addresses scheduling, resourcing, financing, communication, risks, constraints, assumptions, and dependencies, in line with the project management frameworks adopted by the enterprise (such as PRINCE2 or PMBOK)
• To secure formal approval to proceed
• To understand the impact on, and of, other enterprise architecture development cycles ongoing in parallel

Outputs

• Approved Statement of Architecture Work
• Scope and constraints
• Plan for the architectural work
• Roles and responsibilities
• Risks and mitigating activity
• Work product performance assessments
• Business case and KPI metrics
• Project Request and Background
• Project Description and Scope
• Overview of Architecture Vision
• Managerial Approach
• Baseline Application Architecture, v0.1
• Change of Scope Procedures
• Roles, Responsibilities, Deliverables
• Acceptance Criteria and Procedures
• Project Plan and Schedule
• Support for Enterprise Continuum
• Signature Approvals
• Refined statements of business principles, business goals, and business drivers
• Architecture principles
• Capability Assessment
• Business Capability Assessment
• IT Capability Assessment
• Architecture Maturity Assessment
• Business Transformation Readiness Assessment
• Tailored Architecture Framework
• Tailored architecture method
• Tailored architecture content (deliverables and artifacts)
• Configured and deployed tools
• Architecture Vision
• Refined key high-level stakeholder requirements
• Baseline Business Architecture, v0.1
• Baseline Technology Architecture, v0.1
• Baseline Data Architecture, v0.1
• Baseline Application Architecture, v0.1
• Target Business Architecture, v0.1
• Target Technology Architecture, v0.1
• Target Data Architecture, v0.1
• Target Application Architecture, v0.1
• Communications Plan
• Stakeholders
• Communications Needs
• Communications Mechanisms
• Communications Timetable
• Additional content populating the Architecture Repository
• Whatever is in the Architecture Repository e.g.
• Architecture Framework
• Standards Information Base
• Architecture Landscape
• Reference Architectures
• Governance Log