Why technical readiness?
Technical readiness requires a thorough look at your existing service systems to identify issues that might occur in moving to a digital service.
What is technical readiness?
Technical readiness is about checking to ensure that all the potential risks associated to your systems are being considered and managed. It starts through awareness. Is your team aware of the issue and do you have understanding of the impacts.
For each legacy system
is this system available externally to TC?
is there an api to interact with the system?
will this system continue to be used or will it be replaced?
are there systems upstream/downstream that rely on this system?
list the technologies associated to the system
will the digital service need to integrate with the legacy system?
will legacy data need to be migrated from one system to another?
Technical readiness workbook
Use the technical readiness workbook to capture answers to key technical readiness topics.
Access the technical readiness workbook here
What types of issues might technical readiness uncover?
Legacy systems integration
Legacy systems may be used to process and do service processing and fulfillment. In order to not interfere or disrupt service processing and fulfillment it may be preferred to have a digital form write content directly to a legacy system upon submission. While this may be possible, this type of integration work requires a technical deep-dive to ensure integration is possible without interfering with existing legacy system features and functions.
System replacement
Legacy systems may need to be replaced by the new service. It is necessary to do a complete and thorough analysis of the legacy system to ensure that no features of the the legacy system are overlooked.
0 Comments