Technical Debt
Overview
Inefficient applications slowing down your agency operations? Ignoring application technical debt can be costly. When we focus more on maintenance rather than efficiency, the inevitable happens: costs increase, stability declines and security becomes nonexistent.
How to Request Service
Contact your IT Director or Agency IT Portfolio Manager or submit a ticket in the Customer Service Portal below.
Customer Benefits
More Efficient Operations
Reduces operating expenses and improves time to value
Stable App Environment
Maximizes resiliency and mitigates security risks
Steps Toward Modernization
Positions applications for modernization efforts
Service Description
Management and support of application technical debt
Technical Debt services strategically identify and eliminate application technical debt to position your agency for application success and modernization. This service delivers a stable application environment for optimized business solutions and enables more secure and efficiently running applications.
Related Services
Service dependencies could include:
Ecosystem/system environment
Security risks
Technical domain knowledge (e.g., who knows the code, server, or database behind the application)
Customer Responsibilities
Customer is responsible for reviewing and approving long-term Operations & Maintenance plans, as well as providing any applicable application licenses, tools (e.g., system monitoring tools), databases, and hardware that may be required to successfully execute the service.
Service Notes
The Interagency Agreement will outline roles, responsibilities, and processes for implementing the operations and maintenance agreement with the appropriate escalation points for all parties.
Sunset dates and declining utilization are important factors to consider when addressing technical debt. These will be taken into consideration along with OIT’s application lifecycle management process.
Service Owner
Service Levels
While focusing on application quality, an established release cadence will include metrics for measuring deliverable business requirements that will result in usable applications solutions.
Success Measures
Security risk factors identified during development
Standard accepted compliance and development requirements (e.g., best coding practices, IV&V findings)
Agile metrics (e.g., burn rate, release on time and code quality)
Service Support
How to Get Help
Call 303.239.HELP
Submit a ticket in the Customer Service Portal
Hours of Support
Monday-Friday, 8 a.m. to 5 p.m, excluding holidays
After hours service support may be required to meet communicated milestone dates or for technical guidance during the post go-live period.
24/7 Major Incident Management
Call 303.239.HELP
Access a live agent via Customer Service Portal Chatbot
Service Costs
View detail on current utilization here: OIT Common Policy Real-time Billing website