Slides from The BCS EA Conference in London on the 17th July - Focus was on the group exercise of defining and linking architectural artefacts with various project types

1. Enterprise / Solution
Architecture Workshop
Daljit Roy Banger MSc FBCS17st
July 2017
EA SIG

2. Refer to Vote
Workshop Quick View

3. Workshop Objective
Most notional representations of an architectural stack provide context to a
framework that allows creation, alignment and recalibration of processes,
practices and patterns to deliver a systems capability of value to an enterprise.
In this workshop 'we' use the notional model to discuss and map some aspects of
architectural / system artefacts when delivering a value adding capability within
both the enterprise, programme and project journeys .
Most notional representations of an architectural stack provide context to a
framework that allows creation, alignment and recalibration of processes,
practices and patterns to deliver a systems capability of value to an enterprise.
In this workshop 'we' use the notional model to discuss and map some aspects of
architectural / system artefacts when delivering a value adding capability within
both the enterprise, programme and project journeys .
• We will exploit and derive a consensus definition of Enterprise Systems
Architecture
• I(DB) will present my notional stack and highlight some focus areas
• We will work in teams to define typical artefacts for each layer (exercise 1)
• I(DB) will present a view of the stack – with typical focus areas
• We will work in groups to map these to a typical programme of work(exercise 2 )
• We will discuss the artefacts in terms of when/how to use within a delivery
focused set of methods (Classic, Agile, ad-hoc) (Group)
• We will exploit and derive a consensus definition of Enterprise Systems
Architecture
• I(DB) will present my notional stack and highlight some focus areas
• We will work in teams to define typical artefacts for each layer (exercise 1)
• I(DB) will present a view of the stack – with typical focus areas
• We will work in groups to map these to a typical programme of work(exercise 2 )
• We will discuss the artefacts in terms of when/how to use within a delivery
focused set of methods (Classic, Agile, ad-hoc) (Group)
Workshop Structure
Outcome
• Common Understanding of Enterprise Architecture
• Appreciation of the appropriate point when / where to use architectural artefacts
• Common Understanding of Enterprise Architecture
• Appreciation of the appropriate point when / where to use architectural artefacts

4. A Definition Of Enterprise Systems Architecture
The Processes, Patterns & Practices associated with the alignment and
re-calibration of the organisational Technology Landscape to that of its
Business Operating Model
DefinitionContext
Refer to Vote

5. Notional Stack

6. The Stack (Methods/Questions)Stack Decomposed

7. An object of value, which in many cases can be re-used to
control, inform and direct the work of architects in delivering a
capability that allows them to manage the technology
landscape of an organisation. The objects can either be a
documented or digital view/representation.
Architectural Artefact
Refer to
Vote

8. Quick discussion on what EA Encapsulatesor thethingswemust consider
?
Alignment Calibration Create
Group 1 Group 2 Group 3

10. Enterprise Architecture - Example Product Matrix
Control Inform Direct Artefacts
x x x API Management
x x Governance – Process
x x Application - Target Architecture/s
x x Architectural Boards – (Review, Technical, Business Boards(Participation))
x x Architectural Principles - System, Process, Generic
x x x Best Practices Research / Promotion/ Socialisation
x x x Business Architecture Target Definition
x x x Data & Information (MDM Strategy), Journey from Data to Insights
x x x Financial / Funding Models (TCO, Investment Plans)
x x x Gap Analysis – New Solutions, Transitional States
x x x Group / System Policies (Sys Admin etc)
x x x Impact Assessments - Projects, Technologies, Solutions
x x x Infrastructure Target Architecture – Enabling Technology & Platforms
x x Reusable System Patterns (Dev, Integration etc.)
x x Portfolio Advisory
x x x Programme / Project Engagement
x x x Reference Models
x x x Technical / Application
x x x Roadmaps (Product / Technology)
x x x Service catalogue
Strategy (Product/technology, Deviation etc.)
x x x Service promotion Plans
x x x Stakeholder Engagement
x Stakeholder Management
x x Standards / Notations (Promotion of BPMN, UML, Archimate, etc.)
EA Example Artefacts

11. Irrespective of project methodology or approach to
delivering a product or service everything will have
one or all of the following;
Start
Finish
Milestones Set of outcomes / values
Cost
One or many stakeholders
Set of activities
Service Consumers / Producers
Projects / Programmes

12. Classic Project TouchpointsClassic Projects / Programmes
Exercise – Map EA Artefacts to the touchpoints
Prince 2
Waterfall

13. Six Sigma’s
DMAIC
D
I
I
C
C
SCRUM Project Touchpoints
Exercise – Map lightweight EA Artefacts

14. Just f*****g do it - JFDI
Pic Source : Microsoft
• Purely Outcome focused
• Time to Market is Critical
• No thought given to cost
• No Project Structure
Exercise – Map non-structured EA Artefacts
During, Delivery, Post Delivery

15. EA
Concern
EA
Concern
Final Note - Interaction Points – EA / SA
EA
Concern
EA
Concern
EA
Concern

16. Website : www.s-ea-t.com (Tools, Papers Downloads)
Blog : https://dalbanger.wordpress.com/
Email : dal@s-ea-t.com
Thank YouThank You