Wednesday, October 31, the third day of The Open Group Singapore event, started with both a TOGAF® User Group Meeting and a morning track session on Security for the Internet of Things (IoT).
Continuous learning and development – it’s a phrase that can either fill you with joy or fear. Why? Because we all know that the evolving technology landscape, driven by the advancement of AI, IoT, social media, mobile, andcloud technologies mean that our skills always need to be up to date. This is increasingly important as CIOs look to their internal teams to become experts on architecting for cloud environments and cutting through the market hyperbole. We are constantly asked to provide the frameworks, models, and maps that will work as part of a future forward EA strategy.
The Open Group hosted its latest event July 23 – 26 in the Lone Star State at Houston’s Westin Oaks at the Galleria. The theme was ‘Digital Transformation in the Energy Industry’. We welcomed over 200 attendees from 13 countries, including Brazil, China, and the Netherlands.
The number of individuals certified in the TOGAF 9 certification program as of July 2, 2018 has passed 80,000 with certified individuals from 139 countries. This represents over 10,000 new certifications in the past twelve-month period, and certifications in five additional countries.
Following the launch of the TOGAF® Standard, Version 9.2 in April 2018, we now have twelve accredited training providers for our TOGAF® Essentials 2018 course. This short course has been created for existing TOGAF 9 Certified individuals who want to get up to date with the latest changes in the TOGAF Standard and the TOGAF Body of Knowledge in 2018. Options for taking the credential including (virtual) classroom, on-site, and e-learning.
The Open Group TOGAF Standard Version 9.2 was published April 16, 2018. A common misconception voiced by several people at that time was that Enterprise Architecture in general and the TOGAF Standard are barriers to enterprise agility.
This paper addresses that misconception by reference to specific sections of the standard; it does not assume the adoption of any specific agile method.