Archives
-
Communicate highly complex information to a broad audience
One of the common tasks that enterprise architects are dealing with on a daily basis is the need to explain complex IT issues to different audience, including non IT audience and CxO level. I can find many discussions around this requirement but I can hardly find any best practices or advices. In this post I'll try to share my experience and knowledge and I'll be happy to hear other experience as well.
-
Related EA posts of mine
How to retire (respectfully) legacy systems
Information Architecture - The bridge between Business and IT Business Capabilities and Business Strategy
Consolidation of CRM solutions
Creating IT strategy (with a little help from enterprise architecture)
Enterprise Architecture Meta-model, size doesn't matter
Enterprise architecture work Case studies
Using Enterprise Architecture for forecast and implementation of Merges and Acquisition(M&A)
Using Enterprise Architecture to reduce IT costs ( a cookbook for IT cost reduction)
Business Capabilities (a practical guide)
Using enterprise architecture for creating long term IT planning (roadmaps)
What can be done with enterprise architecture
Principles as enterprise architecture outcome
blueprint - an enterprise architecture outcome
How to build practical enterprise architecture team
Modeling application dependencies
Can enterprise architects be young?
Using Hungarian Cube to demonstrate enterprise architecture
Enterprise architecture frameworks are dead, long live real-life practice !
IT('s) Simple!
How to do inormation architecture (in 20 days)
What really makes you Enterprise Architect
Information Architecture (What need to be collected and modeled)
Information Architecture (What is information architecture)
Enterprise Architecture in SAP world
Sorting SA diagrams by EA domain
Reference model for EA definitions and views
What I expect from a vendor EA framework
Business concept
Worktures
It's not SOA it's IT 2.0
10 standards (including standard de facto) that Enterprise Architect should know
Proven way to run your Enterprise Architecture practice
The triangle of complexity and the square of success for EA projects
What is a service (part II)
How to publish your EA work
SOA implementation types, from the Chinese city to the European city
What is a Service
The utopia of one dictionary for the enterprise
How your IT chassis will look like - Part 1
Are your IT vehicles based on one chassis?
Enterprise architecture modeling example
Enterprise architecture is just another systematic approach
SOA, It’s not about the IT It’s about the Business.
Business capabilities or business processes
The Data-Centric Enterprise: A Blueprint for EA - Listen to the audio and watch the - slides! (Running time: 59 minutes)
Does enterprise architecture serve only for long term strategic plans?
Introducing NAAF.
Using enterprise architecture framework to map services and set their granularity
The “Natty” method for monitoring and encouraging systems compliance with the - enterprise architecture
What are Enterprise architecture patterns and how we should define them?
Enterprise architecture 10 common myths -
How to retire (respectfully) legacy systems
They served us for a long period of time, but (for different reasons that I wont cover in this post) now the time to say good bye and to retire them. Legacy systems exist in each and every enterprise and we all have the experience of retire them. The question is whether your enterprise have a predefine process to retire legacy systems or is just process that happened? In this post I'll try to share a retirement process for legacy systems.