The relationship between the CIO and the architects that work for them often lacks a clear line of communication, which can result in a major gap between what the CIO really wants in a well-architected environment and what the architecture team ultimately delivers. Why? Although the CIO might have a high-level understanding of EA's value to the company, he is less likely to provide a clear problem set for enterprise architects to attack, resulting in too much emphasis on architecture design and too little on solving specific problems. Over time, it is primarily this lack of defined goals that leads EA teams into trouble when budgets get tight. Getting a clear set of CIO aligned EA goals positions EA to become a more valued member of the IT organisation.
- Oracle drops 219 fixes in October 2019 critical patch update
- Adobe patches dozens of critical flaws in Acrobat PDF products
- The week in security: Women speak out on cybersecurity careers, CISOs struggle for relevance
- Microsoft releases 'tamper protection' for all Windows 10 users to stop malware turning off antivirus
- Microsoft teams up with NIST to help organizations patch faster than they did after WannaCry