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.
- NK hackers use fake Facebook accounts to lead defectors to malware in Google Play
- Customers recommend, spend more with companies that protect their data – so why are so few businesses GDPR ready?
- Are your customers doing enough to help you protect their privacy?
- Cisco's virtual network interface hit by extremely severe bugs: patch now
- Adobe: attackers can hack Windows 7 with this critical Acrobat PDF flaw