How does your organization determine what needs modernization and how do you prioritize within the list of technologies, applications and IT processes that have been determined to need modernizing?
Sort by:
Technical Debt Assessment: regularly assesses the technologies, applications, and IT processes in use and identifies areas where there is a high level of technical debt, or areas that are outdated or no longer supported.
User Feedback: User feedback plays a crucial role in determining what needs modernization. This can come in the form of direct feedback from customers or internal teams who use the technology, application or IT process in question.
Industry Trends: Keeping track of industry trends helps AI identify new and emerging technologies that can be used to replace outdated systems.
Business Requirements: AI also considers the changing business requirements and identifies areas where new or updated technologies can help meet those requirements more effectively.
Once the areas in need of modernization have been identified, AI prioritizes the modernization efforts based on the following factors:
Business Impact: The modernization efforts are prioritized based on their potential business impacts, such as increased efficiency, better user experience, or increased revenue.
Technical Feasibility: The feasibility of modernizing a technology, application or IT process is also taken into consideration, including the time and resources required to complete the modernization effort.
Risk: The level of risk associated with modernizing a technology, application or IT process is also taken into consideration. For example, the risk of disruption to existing systems or the risk of data loss is considered.
By considering these factors, AI is able to prioritize modernization efforts and ensure that the most impactful and feasible efforts are tackled first.
Thank you for very thoughtful reply. On the subject of technical debt, aside from the obvious out of support and end of life assets, how would you define what else is considered a technical debt?
We review from several perspectives.
1. End of life, no support, no security patches, known security issues.
2. Number of employees using and across how many divisions
3. Revenue flow through the application
4. Government security requirements if used on teams doing government work
5. Roadmap placement on overall business strategic plan to consolidate and reduce various application footprints.
6. ROI on the actual replacement or consolidation
These factors can be weighted differently by each divisions IT Business Partners which then requires some debate to come to an agreed upon prioritization and action. We always have more items for the year's budget than we have budget, staff, or solutions to accomplish.