How to Establish a Technical Baseline
Establishing a technical baseline is the first step to addressing the technical debt. The term refers to a documented and agreed-upon set of specifications, plans and requirements that serve as a foundation for developing, implementing and evaluating a system or technology.
The Department of Defense, for instance, provides the DoD Architecture Framework 2.02, which the military branches can repurpose for this effort. The framework outlines how a system or technology should be designed, built, documented and operated.
Without this kind of framework — or in instances where documentation failed to happen as technology was developed — an agency is put in a difficult position. Instead of moving forward on modernization, an IT staff will have to spend time and energy understanding how legacy systems were designed and built. They’ll also need to determine how the systems evolved, including identifying security patches and system changes.
For more information, agencies can also examine the original documents related to requests for proposals and establish grading criteria to measure whether or not technology met mission demands over time. Using the same criteria, they can then decide to either port legacy technology to an updated supported technology stack or build something new.
Once a technical baseline is complete, the final step is to cultivate detailed interdependency service mappings of all systems to develop redundancy within the enterprise.
DISCOVER: Agencies can upgrade systems on a budget.
Why Are Interdependency Service Mappings Necessary?
In the Information Technology Infrastructure Library framework, interdependency service mappings identify and document the relationships and dependencies between IT services.
Interdependency service mappings help illustrate how various IT services rely on each other and how changes or disruptions in one service can impact others. They involve analyzing the dependencies between services, including technical and nontechnical ones.
These mappings are designed to:
- Identify critical dependencies. By mapping interdependencies, an agency can identify single points of failure within its environment. This will enable IT staff to prioritize and manage these dependencies effectively to minimize the impact of any disruptions or changes.
- Assess impact. Understanding interdependencies lets an agency assess the potential impact of changes or incidents on other services. For example, if one circuit goes down, what are the ripple effects? This helps in planning and implementing changes in a controlled manner, reducing the risk of unintended consequences while lowering technical debt.
Please note, however, that if everything becomes a priority, then nothing is a priority.
- Improve service resilience. By identifying and addressing interdependencies, an agency can also enhance the resilience of its IT services by developing redundancy within its environment.
- Support incident and problem management. Interdependency service mappings can provide valuable insights during incident and problem management processes. Mainly, they help identify the root causes of incidents and problems by tracing the impact across interconnected services.
Service mapping diagrams, dependency matrices and service catalogs can be used to create interdependency service mappings. These tools help visualize and document service relationships, enabling better understanding and managing interdependencies.
As government agencies modernize their technology infrastructures, they must recognize that operations increasingly rely on digital technologies and capabilities. To succeed in this effort, agencies must slow down and understand what technology they already have. This will be slow and tedious work, but it is critical to develop future capabilities and fulfill agencies’ missions.
