TOGAF ADM Phase A: Architecture Vision Objectives
Develop a high-level aspirational vision of the capabilities and business value to be delivered by the architecture.
Obtain approval for a Statement of Architecture Work (SoW) that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision.
Secure the endorsement and support of key stakeholders for the proposed architecture project.
Create a clear and inspiring picture of what we want our organization to achieve and how our new systems (architecture) will help us get there.
High-Level: This means we are looking at the big picture, not getting bogged down in all the tiny details. It’s like planning a vacation by first deciding you want to go to the beach rather than deciding which specific hotel to stay at.
Aspirational Vision: Think of this as our dream or goal. It’s what we hope to accomplish. For example, “We want to be the best in customer service” or “We want to make our products available to customers faster than ever before.”
Capabilities: These are the new skills or functionalities we need. For example, “We need a new CRM system to better manage customer relationships” or “We need an online store that’s easy for customers to use.”
Business Value: This is about the benefits or improvements the new system will bring to our business. For example, “Increasing sales by reaching more customers online” or “Improving customer satisfaction by resolving issues faster.”
Putting it All Together
When we say “Develop a high-level aspirational vision of the capabilities and business value to be delivered by the architecture,” we mean:
- High-Level Plan: We’re outlining a broad plan without going into all the details.
- Aspirational Vision: We’re setting a clear and inspiring goal of what we want to achieve.
- Capabilities: We’re identifying the new tools, systems, or processes we need.
- Business Value: We’re explaining how these new tools or systems will benefit our business.
Example
Imagine you own a retail business and you want to improve how you serve your customers. Here’s how you might develop a high-level aspirational vision:
- High-Level Plan: “We want to create a seamless online shopping experience.”
- Aspirational Vision: “Our goal is to become the favorite online store for our customers by offering fast, easy, and enjoyable shopping.”
- Capabilities: “We need an easy-to-use website, a reliable inventory management system, and excellent customer support.”
- Business Value: “This will help us increase sales, keep customers happy, and encourage them to shop with us again.”
By creating this vision, you set a clear direction for what you want to achieve and how your new systems will help you get there. It guides all your future decisions and ensures everyone understands the goals and the benefits to the business.
Get official permission to start a detailed plan that describes the steps and tasks needed to create and implement the new systems we envisioned.
- Obtain Approval: This means we need to get the go-ahead from the decision-makers or leaders in the organization. It’s like asking your boss if you can proceed with a project.
- Statement of Architecture Work (SoW): This is a document that outlines what we’re going to do, how we’re going to do it, and who will be involved. It’s like a detailed plan or contract for the architecture project.
- Defines a Program of Works: This means the SoW will specify all the tasks and activities that need to be done. Think of it as a checklist of everything that needs to happen to build the new system.
- Develop and Deploy the Architecture: “Develop” means to create or build, and “deploy” means to put it into action or use. So, this part is about both making the new system and starting to use it.
- Outlined in the Architecture Vision: This refers to the high-level goals and plans we set out earlier (in the Architecture Vision). The SoW will detail how to achieve those goals.
Putting it All Together
When we say “Obtain approval for a Statement of Architecture Work (SoW) that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision,” we mean:
- Get Permission: Ask the organization’s leaders to officially approve our detailed plan.
- Statement of Architecture Work (SoW): Create a document that explains what we’re going to do, how, and by whom.
- Program of Works: List all the steps and tasks needed to build and implement the new system.
- Develop and Deploy: Plan for both creating the new system and putting it into use.
- Architecture Vision: Make sure our detailed plan follows the big-picture goals we set earlier.
Example
Imagine you want to build a new website for your online store. Here’s how this process might look:
- Get Permission: You need your manager or stakeholders to agree to your plan to build a new website.
- SoW Document: Write a document that outlines:
- What the new website will include (features, design, etc.).
- How you will build it (steps, technologies, timeline).
- Who will be involved (web developers, designers, etc.).
- Program of Works: Detail all the tasks, such as:
- Design the homepage.
- Develop the shopping cart feature.
- Test the website.
- Launch the website.
- Develop and Deploy: Plan for both creating the website (development) and making it live for customers to use (deployment).
- Follow the Vision: Ensure the new website aligns with the initial goals of improving user experience and increasing sales.
By following this process, you ensure that your project is well-planned, approved by the right people, and aligned with the overall goals of the organization.
INPUTS
Architecture reference materials
Non-Architectural inputs
- Request for Architecture Work
- Business principles, business goals and business drivers
Architectural inputs
- Organizational Model for Enterprise Architecture
- Tailored Architecture Framework
- Populated Architecture Repo
STEPS
Establish architecture project
Identify stakeholders, concerns, and business requirements
confirm business goals, drivers and constraints
evaluate capabilities
assess readiness for transformation
define (architecture) scope
Confirm architecture principles (of the preliminaury phase), including business principles
Develop architectuer vision
Define target architecture value and KPI
Identify transformation risks and mitigation activities
Develop Statement of Architecture Work, secure approval
OUTPUTS
Approved Statement of Architecture Work
Refined statements of business principles, goals and drivers
Architecture principles
Capability assestment
Tailored architecture framework
Architecture vision
Draft architecture definition document
Communications plan
Additional content in the Architecture Repo
ARTIFACTS
Matrices: Stakeholder map matrix
Diagrams: Business model diagram, Business capability map, Value stream map, Value chain diagram, Solution concept diagram