On the Art of Predicting Compatibility Regression when Assessing Risk

  In my last blog post: (https://blogs.technet.microsoft.com/gladiatormsft/2018/02/20/determining-an-applications-impact-when-assessing-risk/) I discussed my first recommended vector for assessing an application’s risk: impact to business or organization. In this post, I will discuss the second recommended vector: probability of regression. Internally at Microsoft, we refer to these as technical blockers. Throughout the first 5 iterations of Windows 10, we’ve…


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,…