Migration, new product development, standard software, outsourcing – or perhaps a mix? My decision guidance for your IT modernization.

In my last blog post, I illustrated the central challenges to IT modernization and concluded that due to growing lifespans, legacy systems can increasingly become liabilities. Have you also come to the conclusion that your applications and development technology need to be modernized, and have you worked past all concerns that stood in the way of reorganization? Then it is now time to consider the “how”. Continue reading 

Never change a running system: Our old IT landscape (still) works – so why should we change it? Some companies are highly skeptical. Let’s take a glance at the main obstacles in IT modernization.

At the beginning of 2015, I discussed modernizing IT landscapes and replacing legacy systems, something that often accompanies the process. Back then, I concluded that IT modernization is nowhere near close to completion, despite new technologies and automatic migration processes. Even with digitization putting more and more pressure on the situation. Continue reading 

Many companies’ application landscapes have grown over time and were added to time and again. Complex interfaces, insufficient documentation, and obsolete development environments result in more and more effort. Changing requirements make an IT modernization necessary – does this apply to you, too?

Some time ago, I presented you the four ways of IT modernization in an infographic. Back then, I suggested that deciding which path to take requires careful consideration and can’t happen overnight. Quite often, however, IT administrators already have difficulty in deciding whether to modernize their IT or not.

Continue reading