Today I have produced a shortlist of links interesting about Togaf and Enterprise architecture.
A nice quote from Angelo Andreetto, Senior Enterprise Architect for Zurich Insurance Group in Zurich, Switzerland
Digital transformation is a fantastic way to rethink Enterprise Architecture,
Communication and post review
People actually think that TOGAF must be right because it is a compendium, very large at that, of IT project good practices, because it has so many brand names behind, because of its many followers in IT, because of its many vocal backers whose interests are intertwined with TOGAF, because it has the dominant training and certification market share, because it has its own conferences.
- is Enterprise architecture completely broken? post
This article is particularly interesting since it explains the limits of EA when this domain is understood as basic documentation or a fixed organization.
EA fails when enterprises are treated as discrete systems that can be reduced into smaller problem sets, as traditional engineering approaches or some EA frameworks would have us believe.
- Agile, TOGAF, and Enterprise Architecture: Will They Blend? article
“Is enterprise architecture still relevant when we do Agile?” and “what is the role of an enterprise architect in an Agile organization?” That the question this article is trying to answer.
- For people that are new to the concepts of Enterprise Architecture, this Microsoft MSDN page is useful. MSDN
Indeed there is a comparison of the Top Four Enterprise-Architecture methodologies. The information there are quite old (2007) though relevant. I am particularly fond of real battlefield experiences on using such methodologies. This article is a good start.
- Developing Business Architecture with TOGAF: Business Architecture with TOGAF
These slides illustrate how to implement TOGAF by delivering some key points, in particular the metamodel.
- Togaf posters
This site offers some posters to have a better understanding of Togaf and the Enterprise Architecture Togaf posters
- Enterprise Architecture by the example :
This document is an implementation of Togaf 9 by Birmingham University. It is full of samples and good information to exploit 🙂 Birmingham Enterprise Architecture Framework
- Since everyone is loving TOP and a list of information, that site is a real treasure about Enterprise Architecture. I have collected some useful information:
- 10 reasons to invest in EA
- Drawing box / another way to practice EA
I am loving metrics and this article was really great: 7 Key architecture metrics – IT Total Cost of Ownership (TCO) as a Percentage of Revenue – Total Cost Savings (TCS) – Percentage Of Spend That’s Strategic (PSTS) – Common Services Compliance Rate (CSCR) – Architectural Due Diligence Rate (ADDR) – Sunset Technology (ST) – Business Specific
Finally to conclude a TOP 8 of Enterprise Architecture risks 8 Enterprise Architecture risks
If your Enterprise Architect can’t describe five cases where Enterprise Architecture has failed miserably, it is time to find a new Enterprise Architect.
- Security vulnerabilities and exposures: EA and security should work together to bring state of the art security to the whole company
- Distracting critical staff: Stakeholders often complain that Enterprise Architecture is cumbersome
- Low adoption rates: It is much easier to define an enterprise architecture than to implement the governance required to implement it.
- Increasing solution costs: Enterprise architecture programs are often guilty of over-engineering.
- Decreasing user acceptance: Users often complain that common solutions are less adapted to the needs of their business unit.
- Creating dependencies: common solutions also introduce new dependencies between business units and can create new bottlenecks.
- Project delays: EA processes can delay projects and add excessive overhead by adding unnecessary checkpoints.
- Be careful what you measure: if EA introduces business performance metrics, metrics may also introduce risks and weird behaviors.