EA @ Deakin
Ron Leen - APG Manager
Arnie Phillips - IT Architect
Background
> Architecture & Planning Group
 Formed 7 months ago
 Consists of 4 (orphan) members - no logical relationship to existing org
structure
> A&P Group Priorities have changed over past two months
 Formerly Business Strategy focus
 Shifted to an EA focus
> Some existing EA Products






Eg. Roadmap = IT User Requirements Plan (ITURP)
Prioritised list of IT Initiatives to support Uni strategic objectives
Identified through discussions with Snr Exec & Faculty Deans
Ratified by the IT Governance Group
Specific funding requirements for following year
Forecast funding requirements for subsequent two years
EA @ Deakin
>
>
>
>
The journey so far
Overview of Deakin EA Plan process
The way forward
Challenges, opportunities…
The Journey So Far
> In the beginning…
 Perceptions of ITSD
• No IT strategy; no understanding of IT “health”; no alignment
with budget model; no strategic input; no business consultation;
etc.
 Confidence in ITSD
• Inability to manage or maintain IT current environment; inability
to deliver reliable services; inability to justify technical
decisions; etc.
 Expectations of ITSD
• Forget “the future” (for now) – improve “the current”
> …the 2006 Review of ITSD
The Journey So Far…cont’d
> Recommendations from the ITSD Review
 Develop an IT Plan defining a University wide strategic direction
for IT
 Develop a formal process for succession planning of Deakin’s
suite of applications
 Develop an approach to standardise principles and maximise
reuse of IT assets
 Develop a portfolio approach to IT environment management
 Develop Pgm Mgmt processes to ensure strategic alignment of
project deliverables
 Develop Pgm Mgmt processes to ensure transparency of project
financials
The Journey So Far…cont’d
> The Birth of EA @ Deakin
 ITSD – The logical way to address the Review recommendations
 Snr Exec – The answer to their (our) problems
> What we did…




What is EA?
What were Deakin’s expectations of EA?
How these expectations should be satisfied?
How EA will “fit” at Deakin?
> The Deakin Enterprise Architecture Plan (DEAP) was born…
The DEAP Process
Gov
ern
M a n a n ce a n
agem
d
ent
TDUF
FAPs
DEAP Scope
Deakin Enterprise
Architecture Plan
s
es
si n s
Bu ioritie
Pr
Enterp
rise
Roadm
ap
Strategic
Management
Strategic
Management
tate
re S
Futu finition
De
Strategic
Management
Bu
s
Pri iness
o ri t
ies
cts &
Proje es
v
Initiati
Program
Management
Strategic
Management
Application
Lifecycle
Fit
a
An n d
aly Ga
si s p
e
tat
S
n
nt
re nitio
r
u
i
C Def
Portfolio
Management
Enterprise Architecture
TDUF
TDUF
Funding Allocation
Annual Planning:
TDUF / FAPs
Review
FAPs
FAPs
Operational
Planning
Strategic
Management
Annual Planning
EA Process
Strategic
Future State
Objective
Definition
Definition
Current State
Definition
IT Initiatives
Analysis
Fit & Gap
Governance &
Management
DEAP Scope
Target
Architecture
Baseline
Architecture
Enterprise
Roadmap
Prioritised
University
IT Initiatives
Initiatives
Project
Program
Portfolio
Management Management Management
Present Iteration
Scope
Development
EA
Deliverables
Deakin
Operational Plan
Via Snr Exec
Interviews
Annual Planning:
DEAP Scope
Definition
Prioritised
Application
Lifecycle
Project
Program
of Work
List
Project Initiation,
Project
Implementation
Management
& Closure
“New
Initiatives”
Overlay
Enterprise Architecture
TDUF
Funding Allocation
Annual Planning:
TDUF / FAPs
Review
FAPs
Operational
Planning
Strategic
Management
Annual Planning
EA Process
Future State
Definition
Supported
Current State
Applications
Definition
List
DEAP Scope
Target
Architecture
Baseline
Architecture
Project
Program
Portfolio
Management Management Management
Present Iteration
Scope
Development
EA
Deliverables
Deakin
Operational Plan
Via
Fit &Business
Gap
Governance &
Analysis
Management
Consultation
Enterprise
Roadmap
Annual Planning:
DEAP Scope
Definition
Required
Prioritised
University
Maintenance
Initiatives
Activities
Application
Lifecycle
Agreed
Program
of Work
Maintenance
Activities
Project Initiation,
Project
Implementation
Management
& Closure
“Ongoing
Req’s”
Overlay
The Way Forward
> Make a start – at this stage it’s just theory
> Implementation
 Rework and implement what we already have first
 Take an iterative approach – with frequent deliverables
 “Project” approach to each iteration – using seconded resources
> Marketing
 Selling the concept of EA to IT staff – and managing resistance
 Selling the benefits of EA to Senior Executive and Business Units
> Education
 What is EA? - What is EA at Deakin? – Why EA?
 Focus training/education to suit specific stakeholder groups
> Commitment and Support
 Appears to be strong executive support – we will test this
 Acceptance that it won’t happen overnight, but it will happen…
Challenges, Opportunities…
> Challenges




Establishing a common understanding of EA @ Deakin
Stakeholder support for EA @ Deakin - and what it delivers
Embedding EA into the whole University – not just ITSD
Ensuring EA benefits justify the existence of the EA team
> Opportunities (outside of those ‘direct’ EA benefits)
 ITSD gains credibility as a disciplined and valued part of the
University
Thank you
Arnie Phillips - IT Architect: arnie@deakin.edu.au
Ron Leen - APG Manager: ron@deakin.edu.au