Company – Architecture Practice Drumbeat
Architecture Services
Delivery Services
Service
P1 - Statement of
Direction /
roadmap
P2 - Policies &
Principles
P3 - Standards
P4 - Design Pattern
P5 - Proposal
Review
Delivery
Services
D1 - Solution
Vision
D2 – High Level
Solution
Architecture
D3 - Program
Architecture
D4 - Solution
Design / Detailed
Design
D5 - Governance
Phase 2
Options
Assessment
& Selection
Consider
Opportunity
Assess
Options
Phase 3
Define &
Approve
Define
Solution
Phase 4
Design &
Deliver
Finalise
Design
Phase 5
Evaluate &
Close
Phase 6
Reflect &
Realise
P2
P5

D1
D2

Evaluate
Delivery
Assess
Effectiveness
P3
P4

Plan
Concept

Select
Preferred
Solution
Plan
Project

Prepare &
Commence


P5
COMPLEX
Business Case
Part C
D4


Design &
Deliver
Document
Lessons Learned
Reflect on
Successes

COMPLEX
Business Case
Part A

D1
COMPLEX
Business Case
Part B
Source &
Allocate
Funding

Test

FID

Sign
Off
Phase 1 / Gate 1
Approval (Via
Gating Checklist)
(Horizon Power
Steer. Co.)
Phase 3 / Gate 3
Approval (Via
Gating Checklist)
(Horizon Power
Steer. Co)


Realise
Benefits
Phase 6 / Gate 6
Approval (Via
Gating Checklist)
(Horizon Power
Steer. Co.)
A principle synthesises an understanding of business or architectural strategy to provide directional statements in
areas that are considered to be important or deal with a recognised area of conflict. A Policy defines a mandated
way to use business technology efficiently. Policies can be developed across all domains.
A standard is a mandated product or specification for deploying or using a specific business technology.
Standards are to be developed and maintained on a regular basis.
Enterprise Architect
A preferred specification for solving architecture problems. Patterns should be developed for common or likely
recurring architectural challenges.
This Proposal Review service assesses and provides input to the development of the Business Case (non-complex
and complex). The review includes consideration of architecture importance, impacts, synergy, considerations for
the next phase, broad costing band. No solution is to be provided.
The Solution Vision is a scope setting document created early on in the project lifecycle, intended to build
consensus between stakeholders on the high-level view of the solution to be delivered. This document is to
inform the Business Case as to the feasibility of the initiative.
Architecture Service
D3
Phase 4 / Gate 4
Approval (Via
Gating Checklist)
(Horizon Power
Steer. Co.)
Phase 5 / Gate 5
Approval (Via
Gating Checklist)
(Horizon Power
Steer. Co.)
Responsibility
Enterprise Architect
n
Phase 2 / Gate 2
Approval (Via
Gating Checklist)
(Horizon Power
Steer. Co.)
Close
Project
Description
This is a primary EA deliverable produced using an adaptation of the TOGAF ADM, to research, analyse and design
changes to address a particular part of the business, or address a particular business issue. Involves:
Architecture Gate
D5
END
Type
Planning
Services
Phase 1
Concept
START
Planning Services
P1
Implementation at Company
What services are currently provided?
Enterprise Architect
Solution Architect
Enterprise Architect
Enterprise Architect
Solution Architect
Solution Architect
The solution architecture provides a high-level design of the solution to be developed. This document is to inform
the Business of the solution being proposed in sufficient detail to allow the business to understand the solution
and accept the risks of proceeding with the project.
The program architecture captures the high level design of the current and future program solutions to be
developed covering all the projects to be delivered and the multiple program transitions stages/periods.
The Solution Design, currently Detailed Design or PTM, is the detailed design of all facets to be implemented
including all interaction between new and existing processes and systems.
Solution Architect
Monitor solution compliance to agreed architecture
Solution Architect
Solution Architect
Solution Architect
What services need to be provided on a regular basis?
What is an appropriate name for each for the services?
Are they placed in the correct place in the PMM (above)?
What are the right places for compliance checks?
Company – Architecture Practice Drumbeat
Architecture Governance
The Architecture Review Board should:
• Guide architecture effort and output to support the success of Company’s business objectives;
• Review and endorse architecture deliverables (Statements of Direction, Principles, Reference Models, Roadmaps, Standards, etc.);
• Ensure the effective implementation of the architecture by:
• Enforcing Architecture compliance across the organisation;
• Identifying divergence from the architecture, provision of dispensation and planning of activities for realignment;
• Providing a point of escalation for architecture issues, disputes or unresolved architectural choices;
• Sponsor the effective operation of the EA Office and champion EA Services and deliverables;
• Validate EA performance reports and EA derived benefits
The Design Authority should:
• Have representation from Plan, Build and Run areas of ICT;
• Review architectural solution designs to ensure compliance with agreed Principles, Standards, Reference Models, Roadmaps,
etc.; providing either approval or direction for realignment;
• Consider the validity of requests for exemption / dispensation from agreed Principles, Standards, Reference Models,
Roadmaps, etc.;
• Clarify and communicate architectural direction for Project Delivery areas;
• Consider impact from business-as-usual activities on current or target architectures;
• Identify gaps in the Enterprise Architecture critical to effective governance of Project Delivery activities;
• Provide a review function for new architectures and standards (as needed).
Implementation at Company
What governance bodies already exist? How well are they functioning?
What has been tried in the past? What do you think would work?
What names make sense?
(i.e. EA Office may be better termed Architecture Office or EA Function; Design Authority may be called Solution Review Group or Technical Review Group)
What are your thoughts with regard to OT governance, is the ARB a shared function?
Architecture Practice Drumbeat
Architecture Charter (example)
Implementation at Company
The Architecture Function exists to:
1.
Guide consistent and cost effective investment that directly supports Company’s strategic objectives; and
2.
Provide the support and solution assurance to ensure projects progress strategic objectives.
What would you like to see included?
The objectives of the Architecture Function are achieved by:







Identifying and supporting innovation ;
Collaborating with business stakeholders, ICT management, project teams and support areas in the
development and maintenance of (current and future) holistic architectural descriptions of business
capabilities, information, services, application and technology environments;
Developing maintaining and publishing roadmaps that guide change in the operational management of
Company’s IT assets in such a way that it supports the business strategies and aligns to industry best
practice;
Participating in Business and ICT (long and short term) planning activities, providing impact analysis and
advice regarding architectural interdependencies;
Proactively resolving Architectural issues important to the organisation;
Communicating the architecture activities and direction;
Monitoring compliance of project delivery activities.
Architecture Value Measurement
Benefits indicators:
• % improvement in speed to market (product design to delivery cycle time)
• Performance improvement (business efficiency resulting in operating cost reduction or SLA
improvements)
• Rationalisation (usually ICT related system support and maintenance cost reduction)
• Avoidance of risk (business operations / customer risk)
• Improved alignment of project(s) to strategic objectives
• Cost and effort saved for projects by reusing existing IT services
• Opportunity identification (resulting in innovation or planning / delivery efficiency)
• Improved Business Value (contribution to Company reportable KPI’s)
Productivity indicators:
• Number of White Papers / Briefing Papers / Architecture Decisions
• Number of Business Planning meeting (Group Level) contributions
• Number of POV Reviews / Number Impact/Risk Assessments
• Number of Projects supported, and effort provided
• Number of Requests for Architecture in the pipeline; in-flight; delivered
• Number of Project Solutions assessed for compliance; number of Projects self-assessed
• Number of compliant / non-compliant project solution architectures
• Number of hits on EA Website per month
Implementation at Company
What measures make sense to the Company KPI’s?
What is it practical to capture? (i.e. do not be unrealistic in
measuring too much)