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.
- UK MPs call for a cyber security minister to defend critical infrastructure
- Instagram bug exposes user passwords
- BlackBerry's acquisition of Cylance raises eyebrows in the security community
- Authentication bug locks users out of Azure and Office 365 for a day
- The week in review: Cybersecurity breaches named the biggest risk to business… and healthcare… and sports… and…