A few weeks back I sat in on a TOGAF 9.1 training course that I had my team ramp up on. This training was two fold, up-level the knowledge of enterprise architecture team on EA methods and it also served as a tool to understand the gaps in our own EA Framework (which is based on TOGAF) and enhance for our next stage of maturity.
Throughout the training I observed several misconceptions, open questions and even some concerns with TOGAF. As I sat and listened I reflected on what I’ve heard about TOGAF in the past. They were all very similar to the debates I hear on Linkedin, Twitter, blogs and many other forums. Some have a lot of merit while others not so much.
So, I jotted a few of the big ones down with a little bit of context and thought I would generalize them into something that would be useful for all of you to leverage or learn about. I am going to check the EA dogma at the door and be as factual as possible. It’s important for us to factually all about this topic and not get burdened by option or bias.
Below are the myths or facts I will create posts for in this TOGAF Demystification series. Expect this to flow out over the course of the next few weeks:
- TOGAF Sucks: Incomplete and Complex
- TOGAF vs. [Insert Architecture Framework Here]: What you need to know about comparing frameworks
- TOGAF Certification is a Weak
- TOGAF Certification = Enterprise Architecture Certification
- TOGAF = Open Group
- TOGAF is too Ridged and Academic
- TOGAF is a Framework
- TOGAF is Enterprise IT Architecture (EITA) not Enterprise Architecture (EA)
If there are any other topic you want me to cover, please leave a comment. I would love to hear your thoughts as well.