{"id":407,"date":"2007-10-09T07:00:05","date_gmt":"2007-10-09T15:00:05","guid":{"rendered":"http:\/\/www.formtek.com\/blog\/?p=407"},"modified":"2007-10-09T07:00:05","modified_gmt":"2007-10-09T15:00:05","slug":"technology-enterprise-architecture-failures-are-rampant","status":"publish","type":"post","link":"https:\/\/formtek.com\/blog\/technology-enterprise-architecture-failures-are-rampant\/","title":{"rendered":"Technology: Enterprise Architecture Failures are Rampant"},"content":{"rendered":"

Most people believe that simple is better. And it is. Simple things done right are ‘elegant’, ‘sleek’ and ‘powerful’. Companies that focus on product simplicity often can achieve amazing success — Apple is a good example. People always tell each other to keep things simple — K.I.S.S. But yet, the simple approach usually isn’t selected, because it is too hard.
\nWhy is it that Enterprise software isn’t simple? Simplicity is usually the exception rather than the rule. Businesses are too complex, or company business processes are too ‘unique’ to easily fit the mold of out-of-the-box software? Or do vendors just miss the mark too badly? Software doesn’t need to be complex. Software applications designed with a minimal set of high-value superbly-executed core features are consistently preferred to more feature-full and bloated alternatives.<\/p>\n

The state of Enterprise software projects isn’t good. Gartner is predicting that 40 percent of enterprise architecture projects will fail between now and 2010. Over the next year they predict that 25 percent of CRM projects will be canceled because of lack of consultants and system integration skills<\/p>\n

Gartner’s prescribes <\/a>the following three approaches to minimize risk in large-scale enterprise projects:<\/p>\n