Determining an Application’s Impact when Assessing Risk

In my most recent blog (https://blogs.technet.microsoft.com/gladiatormsft/2018/02/14/leverage-a-risk-based-approach-to-application-compatibility-testing/) I discussed how successful shifts to managing application compatibility involve moving to a model that prioritizes testing according to risk factors. The model I usually recommend to customers is to apply a common two-dimensional graph based on two primary risk factors: Impact to business and the application’s likelihood of…


Leverage a Risk-Based Approach to Application Compatibility Testing

Once upon a time, application compatibility projects usually followed these basic tenets: 1.)     Find all the applications being used. 2.)     Rationalize as much as possible. 3.)     Thoroughly test as many as possible. 4.)     Repackage all the applications. Depending on the size of the portfolio and the number end-users, these projects lasted from 9 to 12…


How Detailed is Your Enterprise Application Catalog?

Over the past several years, I have been involved in many application projects. Whether the project was centered around packaging, virtualization, or compatibility testing for operating system migrations (as my specialty is now) a variable for success was and remains – the enterprise application catalog. You’ll read synonyms for this as well (including package store,…