Technical debt describes the dependence of applications on technical components. The business question What is our technical debt? focuses on the dependencies of the applications in the application portfolio and highlights their dependencies on technical components based on lifecycle data.

Look for conflicts in the end dates of the applications and their dependent components and analyze lifecycle conflicts according to different time scales to support better planning and transparency. A technological component with an end date before the end date of the application is potential source of risk and increases the technical debt of your IT portfolio. With this information, you can address the technical debt before the application or component goes out of service and prioritize applications that require immediate migration. This business question ensures that you address the most urgent requirements for application migration or updates that are important for regulatory requirements but allows to effectively plan ahead.

The Gantt chart shows all active or planned applications that have at least one component with an end date before the application end date.

• To understand which active applications are running on obsolete components:

  Select already obsolete in the Lifecycle Conflict filter. To understand which components will be obsolete soon, select within six months.

• To understand the impact of obsolete components on the business:

  Select a business capability in the Business Capability field to understand potential lifecycle conflicts that may prevent application support to the business capability.