Subject: Request for Inputs on Defining Application Maturity and Complexity
Hello Team,
As part of an effort to enhance Tech Operations for the 100+ applications under my support, I am adopting an approach that begins with assessing the Maturity and Complexity of each application. This assessment will help prioritize efforts by focusing on applications that are high in complexity and low in maturity.
To determine these rankings, several KPIs will be considered per application, including (but not limited to): number of incidents, service requests, servers, databases, associated APIs, upstream and downstream systems, number of users, and user feedback (likes).
I would like to seek your input on the following:
1. How do you define the Maturity and Complexity of an application in your context?
2. Do the models used for benchmarking Maturity and Complexity share overlapping attributes or KPIs?
Your insights on this would be highly valuable. I greatly appreciate your time and thoughts on the matter.