Software Monitoring and Technical Debt Policy

EFFECTIVE DATE: October 18, 2021

APPROVED BY: Mike McCoy

LAST UPDATED: October 18, 2021

PURPOSE

The purpose of this document is to establish the policy regarding the monitoring and governance approach regarding technical debt and Open Source Software (OSS) to be used by all software project teams within Innova Systems, International LLC (ISI).

SCOPE OF THE POLICY

This policy defines standards for monitoring of OSS and technical debt and is applicable to all ISI software development project teams.

APPLICABILITY

Responsibility for maintaining creating and maintaining an effective software monitoring program is divided between Development Mangers, Architects and Project Leads. Project Leads must ensure the team is adhering to this Policy. Development Managers and Architects must coordinate the procedural details to align to established guidance activities.

AUTHORITY AND COMPLIANCE

This policy is authorized by the Chief Operating Officer (COO) and compliance with this policy will be evaluated through an appraisal/audit process. Results will be provided to the appropriate personnel and non-compliance/issues will be submitted to the Business Unit Leads and the Executive team for remediation as part of the Monthly Operations Metrics Reviews.

POLICY STATEMENT

The ISI Software Monitoring and Technical Debt policy has been introduced to establish a structured set of minimal policies, activities, and artifacts to maintain an effective program. While this program will include activities spanning the organization, a primary area of focus will be ensuring OSS obsolesce and technical debt is monitored and responsibly managed to avoid security ramifications and excessive velocity challenges associated with onerous rewrites.

InnovaSystems project teams shall:

  1. At regular sprint intervals, examine and evaluate emerging technical debt and OSS obsolesce
  2. Create and manage a backlog of all significant technical debt and OSS liabilities
  3. Estimate the size and scope of managed liabilities
  4. Prioritize work related to managed liabilities in conjunction with other story/feature types

Process Guidance Version: 10.4