Season 8 of Architecture Corner with only female guests
Sally Bean, Soina Sharma and Petra in’t Veld Brown talks about their views of Enterprise Architecture and why there are so few female architects.
This episode was recorded at British Computer Society in London, UK
See more episodes from Architecture Corner at https://youtube.com/c/architecturecorner
© Artmann Media 2020 www://www.artmann.co.uk
Creative Commons License - Attribution Share Alike
I’m now assisting a global company with enterprise architecture skills.
The organisation are changing to new business models and I use the same approach here for Enterprise Architecture as for my filmmaking company in the EA case study.
We start with the business model canvas, look at APQC processes as input for new processes. Then continue step by step until consumers can use the service all over the world.
Very straightforward, but not as easy as taming a wild horse.
What should a basic reference architecture contain?
These are the artefacts I use when doing a reference architecture for larger organisation.
Level 1 and level 2 processes
Key business objects
Key business metrics
Information components / groups
Key actors
Critical business use-cases
Main applications
Business critical integrations
Main stakeholders
High-level organisation chart
Constraints
The purpose of the reference architecture is to be a long term guide for development and/or transformation in a business unit or on a higher level. It must fit the future business model and include both business and IT-aspects.
From these part, you can compose a number of views for different purposes and stakeholders.
When you start a digital transformation you need to mind the gap. This us especially true if your are a traditional manufacturer who sells physical products and you will start to sell services directly to consumers.
Photo: Adobe Stock
There is a huge gap between business models from the past to the future.
This leads to another gap in the core processes when you do new things. You have to work different.
With different ways of working, you probably need new skills, so the organisation needs to learn.
Do you now think that your legacy IT systems are suitable for a new business model, new ways of working and users with new skills?
Mind the gap so you don’t stumble.
Do you need maturity models to evaluate progress in capabilities and behaviour?
My wife Lotta got a wild horse three months ago and started the basic training with this in mind.
When you buy a ordinary horse, it have aquired a basic set of skills and could be handled by a new owner. On a scale from zero to five, you are on level two or three.
But with a wild horse, never touched by humans before captured, you start on level zero.
If you try to apply methods for traning a breeded horse to a wild horse will you fail. First of all, you have to build trust with the horse by just being near and not touch it.
After three months of daily traing, she was able to sit up an ride.
So the purpose with a maturity model is to understand where to start your ride to progress.
Not that different from digital transformations when you know what you are doing.
