Why Enterprise Architecture?
Vložit
- čas přidán 18. 04. 2013
- Meet Michael, he works at a your company. He needs support from IT to do his job, so they cater to his wishes. But Michael is not alone and many Michaels later a Hairball Architecture will grow unless you use Enterprise Architecture (EA) to prevent that. EA is not just about some guidelines and principles, it is a process that makes sure the constant changes that inevitably happen in your landscape are good for your company as a whole and over time, not just good for the problem at hand.
The animation stresses the chaos-prevention goal of enterprise architecture and only touches lightly on the fit-for-the-future goal of enterprise architecture (at the end). Some architects (see comments below) say it wrongly depicts EA as too much about IT. I've posted a longer reply here: enterprisechess.com/2015/04/27...
The animation and narrative was created by New Narrative (www.newnarrative.media) based on interviews with me (the underlying message is mine, the way it is presented has been designed by New Narrative, I OK'ed the final script).
This animation can be freely used 'as is'. If you want an adapted version, please contact me for the approval (as I represent the publishing rights, info@masteringarchimate.com) and you will need to work with New Narrative for changes (as they are the owner of the animation). McDonalds and the Bank of Scotland are some of the organisations that have made customised versions for internal use.
If you use this for your practice, I'd appreciate that you let me know. I know of several large enterprises that are now using this.
If you want to know more about the philosophy behind this video, go to ea.rna.nl/ - Věda a technologie
7 years after, this video is still relevant. I am using it in a lot of presentations, to evangelize end-users. Thanks a lot!
You're welcome
Am an EA myself and this explains it so soundly and neatly - Great video!!!
Fantastic and precise explanation for what and why Enterprise Architecture required for any organization, i really liked the images used, +1 to the presentation.
II've adapted the description to make sure it is clear you can freely use this and what you must do if you want to have your own adapted version (e.g. with your own company logo or narrative)
Wow
Now I get the idea, thank you very much for making and uploading this video :)
This is such a great video! I remembered it but couldn't find it for ages ...
Thank you! The easiest way to find this video is to search for "Enterprise Architecture" and then it is the one with the most hits :-)
A great video, really amazing summary of EA.
Solid video that I will share with my colleagues to explain why we must mature our Architecture governance.
10/10 explanation and video. Thank you for sharing.
@Gerben Wierda, really appreciate the effort in making such a simple and straight forward video. Hats off to all the drawings and the person behind the drawings :)
Thank you.
He's using a whiteboard video maker.
Great! The best ilustration about EA ever!
Best presentation on ea. Good job man👏👏
a great video for briefly introduction . look forward to more deep explanation.
More in depth (and more up to date, e.g. on agile/devops and architecture: ea.rna.nl/ And have a look at the other (longer) videos in this channel. There are only a few, but they are more in depth (thus also longer).
Amazing presentation....
supereinfache Zusammenfassung - perfekt! Werde ich demnächst bei einen Studenten verwenden.
you forced me to watch the video till the end
what magnificent presentation
wow this video is great. you sum up pervect what EAM is about. Thank you
What a good and easy explanation.
Very well done video.
Excellent video!
Brilliant ! Thank you !!
Great way to explain.
Great explanations.
Very good explanation..
Just awesome! Enterprise architecture is much more than just IT. Its basically defining how the enterprise should function to be effective, Robust and flexible at the same time. Enterprise here mean Business/NGOs/Government/Group. In plain and layman terms, Enterprise Architecture is needed to translate human idea/s into reality in a systematic and time bound manner.
See ea.rna.nl/2015/04/27/the-great-escape-ea-is-not-about-it/ and ea.rna.nl/2017/01/13/agile-architecture/ and the video czcams.com/video/d10A21OepgA/video.html
Brilliant video which helps when communicating with stakeholders so they quickly grasp why EA is a muss. Thanks for the great video.
Thank you.
Well made and lucid
Subtitles in Dutch, German en English (perfect copy of audio) have been added.
Great Video Gerben! Is it possible to add a Portuguese (Brazilian) subtitle?
Dear Gerben! I made an audio synchron of your fantastic video, which is available as unlisted. Since I used youtube video, therefore I had to remake the entire audio channel.
@@tnacsak And this means?
@@GerbenWierda I did not now the rights of re-usability and wanted to inform you. I do not think that you need to use the Hungarian version, but if you do I share you the link. On the other hand I hope this change was legal, but anyway thanks a lot for the great content!
@@tnacsak Contact me via email. Send me the link.We can see if I can add the audio as an option to the original here.
Which software used to create these kind of illustration videos , if any one can advise.
This has not been created by software but by a real human. The human was filmed while creating this (it is a real human's hand you are looking at). Some scenes were pre-drawn as a start, then making additions were being filmed. Some after-processing and editing has taken place.
A perfect introduction
Nice Explanation for dummies ;) !
Excellent!
What are all the properties of the enterprise IT infrastructure does enterprise IT architecture ensure?
If you ask me, mainly one property: most of it will be about agility. See ea.rna.nl/2020/02/11/a-tipping-point-in-the-information-revolution/ and the final link in that article's PS.
well explained thanks
What you call "hair ball" architecture is often referred to as "spaghetti architecture" and it is driven from the more known term of "spaghetti code". Great video.
.. Shadow IT is another term that often pops up too.
I do agree with you as well as the term "Spaghetti" is more nice
The Prologue of Chess and the Art of Enterprise Architecture is called "Loosely Coupled Spaghetti" and is available as a free download: ea.rna.nl/the-book/
I like this video, it gives us a view on EA from the viewpoint of non architects. It is all there, the perspective chosen is one most enterprise stakeholders will recognize. And is this not an important aspect of EA: communicate with views on the subject at hand in a way your stakeholders understand
I do agree on the comments EA is NOT mainly about IT and should focus on all aspects of the enterprise. I do also agree on the response that IT is an important part of an enterprise today and therefore IT must be part of EA.
I regret the video does not really explain EA should cover transformations from one perspective to an other (rows in the Zachman framework). This to ensure all stakeholders understand what, how, when, where, who and why from their perspective, aligned with the other perspectives. The viewpoint (or perspective) the video shows makes it look like EA is about IT architecture although if you look closely you see it mentions more then IT alone.
The Enterprise Architect must ensure enterprise strategies are developed into business concepts which in turn are developed into business logic (systems, not only IT systems), technology, tools and instantiation.
The other way around EA should help to change the current instantiation of the enterprise into a modified instantiation which solves actual problems AND fits in the remaining (unchanged) enterprise strategy, business concepts, systems, technology, and tools.
If you keep this in mind, this video gives a good overview which can be used to inform, convince, our stakeholders why EA is not optional and helps to create Business Value.
Nice graphics!
Great video. Who created the video and did the sketch work?
Alyssa Farr If you expand the information it gives that information: The firm T36.
Awesome...
Dear Friends,
I have read TOGAF v9.1, I have some questions to ask again so that I understand correctly and fully, the questions are as follows:
1/ The ABB (architecture building blocks) will be technology independent, right?, and it is used to describe Target models in Phase B,C,D?
2/ The SBB (Solution building blocks) is tied to specific technologies (eg Cloud, Microservices, etc.), right?, and it is used in Phase E?.
3/ The Technical reference model is used in Phase E, right?.
Dear ytuong, EA is not the same as TOGAF, nor is the reverse true. In my opinion TOGAF is seriously ineffective in the real world. You may have a look at the Chess and the Art of Enterprise video (EAC 2016 keynote) in my channel. Feel free to use TOGAF, but in the countries where it was first promoted it has never gotten a serious foothold for the reasons explained in that keynote.
@@GerbenWierda , what model replace TOGAF?
@@ntcuong01ct1 There is not a framework I can advise. I do not use a framework at all, unless you consider 'EA Chess' a framework ;-). czcams.com/channels/Tqv-dxJc_nMsZqBYJW3iCw.html has two keynotes from Enterprise Architecture Europe on EA (Chess and the Art of Enterprise Architecture from 2016 and Architecture in an Age of Agile form 2018). SAFe pays some attention to architecture, this contains some useful suggestions but for me has the status of ideas, more than a real mature practice.
Very good! I would like to ask about a subtitle in portuguese, Can I translate it? And you add this to the video?
Thanks
I've done this now for German (provided by Swiss customs). I you want to provide Portuguese, contact me and I'll add it.
this is very useful.
Hi everyone, i'm having a research about EA, there's a problem that I couldn't find any real example of EA in reality. Can you please help me out by naming some EA solutions ? and also some company/organizations using these solutions ? Thank you so much :)
It is not quite clear what you mean by 'example of EA in reality', do you mean actual EA documents from organisations? These are generally not public as they are strategic. The same holds for 'EA solutions', probably (depending on what you mean).
There are several 'solutions' for setting up EA functions and processes. Even for the most popular/widespread of these there is little proof that they actually (can) work as intended. You can watch czcams.com/video/tCTqNZW0wIk/video.html and you might look at documents by Kotusev kotusev.com/ (e.g. 'history of' and 'fad' documents).
If you liked this video you might enjoy this 2 minute animation "What is EA"?: ow.ly/v3Qlg
I liked it.
Sorry it took me so long to allow this reply. CZcams had put it in a spam box and I did not really watch the replies on this page so I only just found out. But your explanation indeed fits this video. I like the mentioned notion of sets of models and the 'design' approach to architecture.
I'm currently a first year Computer Science student, I've been doing some research on good career paths to follow in the IT world and I've been quite interested in this. How exactly can I become an Enterprise Architect? What exactly is the path I need to follow to pursue a career like this? Advise from anyone in the field Welcomed :)
+Tobe580 This depends on what people think EA is. Some people think it is some sort of abstract 'architecting of an enterprise', based on high level elements like business functions and so forth. This may be part of it.
Fo me, starting out in software engineering is a good way. Get experienced and grow in ever more large and complex software engineering projects. Soon, you'll encounter both infrastructure and business elements that are important (such as people, process, etc.). After a while, you'll be able to cast your net wider and wider and enterprise architecture comes more or less naturally. You might do an MBA after 10 years of experience or so, to fill in white spots about what an enterprise all is or can be and how it is managed.
The best EAs I've worked with had a deep understanding of the complexities of IT.
I've written a about EA skills in my book Chess and the Art of Enterprise Architecture (bit.ly/eachess).
+Tobe580 Dude, I am an Enterprise Architect. It is a great gig but much of the value/need is going to disappear with the move to cloud/hybrid computing. You would be much better served pursuing a degree in data science. Software engineering is a good start. Today's Enterprise Architects will be tomorrow's cloud architects and data scientists.
+Ricardo Sanchez Data Science is really hot, no disagreement here. But the cloud is not going to make EA superfluous, quite the opposite, I think. Tje fact that the 'broad landscape' of an enterprise gets fragmented over many cloud-based offers makes it only much more important to try to get a grip. 'Your' IT is still 'your' IT from a business perspective, even if it legally is sometimes 'their IT'. See also Data center myopia creates cloud illusions.
Nice Video !
Great video!!! However I differ in positioning the Transition Architecture as being a PSA-deliverable.
In my opinion, PSA-activities are part of the architecture governance, (TOGAF phase E/F/G) aiming on and supporting achievement of (parts of) the next Transition Architecture.
PSA-results are early-project deliverables and as such project directives that are valid while a project is running.
A Transition Architecture is an architecture cycle deliverable, an overall goal as stepstone in achieving the Target Architecture. Most likely the Target Architecture state is or will be the result of running one or more projects.
The Transition Architecture isn't a deliverable of the PSA-phase, its a preliminary. In TOGAF, the Transition Architecture is the cycle-result of phase B, C and D.
I see it's a simple innovative entrance to EA there are many other elements like governance - reosurces - security - business processes ...etc but it still good entry to EA
Thanks. Yep, definitely too simple of course (less than 4 minutes after all). A more in depth treatise is in my other video, but then again, that takes about an hour to sit through.
Cool
these are cool graphics
Gerben is very creative.
Am I the only one that thinks this narrator sounds like the one that guides Stanley?
I have no idea what he is talking about.
I could help, but then I have to know who 'he' is and what the problem is. Maybe a little more than just that single sentence you wrote so that there is something to understand and/or react to?
lala micheal
The early part of the video is true. However, the conclusion that we need committee & bureucracy to solve this problem is very wrong.
Not every form of meeting is 'committee & bureaucracy' and the animation does not propose that. We need collaboration (as nobody can know everything about everything) and we need a consent-based checks & balances. A short video like this cannot go into depth on these and the example given of the checks & balances we need is not by definition bureaucracy. It can be very pragmatic and fast.
Having said that, this video is 8 years old and was made to explain it to people in a setting with projects and up-front project design. The architecture approach itself was already agile, but the projects at that time were still classic (in that case, EA became agile before the change organisation did).
As much as the video is clear, it is also clearly wrong and passively misleading (by omission). The video talks only about technology, and Enterprise Architecture is NOT primarily about technology. Sure technology is a PART of EA, but it is a small part. This video talks about robustness, efficiency, complexity and solution architecture, which are concerns for IT architecture, but NOT enterprise architecture.
EA has been invented to combat the IT-chaos and alignment problems that appeared when systems got linked up on a serious scale. Look at Zachman's initial framework for example. Though approaches exist where the more abstract enterprise development is now put first, I think most of us keep to the anti-chaos and alignment goals.
Mastering ArchiMate
Mostly agree with Nick - it's a great video, but about a proper subset of EA? If it just started with the business perspective and elaborated on the "What they do for the business..." part of the project architecture, it could really nail it...
The history of Zachman's frameworks is interesting - according to www.zachman.com/ea-articles-reference/54-the-zachman-framework-evolution, although he began with an IT focus under the rubric "Information Systems Architecture - A Framework", his view was that "strategy and information systems needed to be "engineered" for the ENTIRE Enterprise, not just "manufactured" by the I/S department" but he worried people weren't ready for this idea. Perhaps they still aren't...
Stuff Nick Likes I've referred to this comment in the following blog post: enterprisechess.com/2015/04/27/the-great-escape-ea-is-not-about-it/
+Stuff Nick Likes Great point. I am an Enterprise Architect and the last thing we want to do is get bogged down in the as-is; especially with cloud computing, the EA role should help create new business models using primarily cloud computing. Focusing on the business/mission value is where EA role excels.
Primarily with Cloud? sorry that is wrong; dont jump to solutions. This may, or not apply. It is likely to feature somewhere at sometime.
This video is a good introduction BUT by the end it suggests an architect role ends when the "ideal future state" plan is created. It is misleading. Architect is involved from planning, designing, through the development process. Unless we assume waterfall approach, we know results & big risks of that approach.
It's definitely not intended that way. And I think it also doesn't say that as most of the animation is about the architecture role during a change process. It just at the end touches on future state. It is based on architecture in an up-front design world (project architecture and so forth) and not the agile methodology for changes, but that doesn't mean architecture itself cannot be agile. Have a look at the other video in this channel for more in-depth and ea.rna.nl/2015/03/08/losing-a-limpet-what-happens-when-we-dont-have-enterprise-architecture/ for a follow up on that for architecture in a setting with agile methodology.
czcams.com/video/tCTqNZW0wIk/video.html is the more in-depth video
I am thinking not about Agile particularly but what is considered Evolutionary Architecture. I like video very much. However, coming back to it a year later, I feel something important is missing, perhaps "Architecture is a snapshot of an ongoing process" rather that a future vision or design.
files.catwell.info/misc/mirror/2003-martin-fowler-who-needs-an-architect.pdf
Yes, I know that one. Nice story. I've used the definition for architecture mentioned in there ("the important stuff") once in a while. It has also a typical software-people problem, the idea that "Software is not limited by physics". While theoretically it isn't (software is logic) the idea that physics plays no role is something that has produced many failures and problems in IT. Software engineers often ignore the physical limits of IT in their thinking (e.g. latency) because *logically* there is no price to pay. But I digress.
I'm all in favour of architecture being very 'fluid' reacting to what happens, with wise things about "the important stuff". But it is about the design decisions that are made. I'm not in favour of using a 'future state' to guide you, instead I am in favour of using the here and now and look at how it can be strengthened (but all of that is in the other video). The suggestion that it is about "where we go" is in my opinion the weakest part of this video, but it was impossible to put all the subtleties in there (less than 4 minutes after all), so we cut a few corners. Though we did mention that you cannot predict the future and you have to be robust under change. But "where we're heading" is indeed problematic in the audio. You've effectively put the finger on a small sore spot in the video, for me too :-)
it's all just buzzwords
Wish there were more women in the video!
That, I think, is understandable. Same goes for any person that is non-white, however that is hard to do with this technique as it is all line drawing on a white background.