As a part of the making of the FTS Technology Landscape we have released the TechRadar as a fast viewer for the status of FTS regarding the technologies of our interest.
The development of common development/computing and delivery platforms has modified substantially the approach to the technologies to be used in order to prepare FTS for the new challenges.
What is the Tech Radar?
The FTS Software Tech Radar is a list of software related technologies, complemented by an assessment result, called ring assignment as categories. We use for now four rings:
- ADOPT — Technologies we have worked in the past, have high confidence in to serve our purposes, even in large scale. Technologies with a usage culture in FTS production environments. We are not thinking of discard these technologies yet.
- TRIAL — Technologies that we have seen work with success in project work to solve a real problem; first serious usage experience that confirm benefits and can uncover limitations. Technologies we have tested in Proofs of Concept with a TRIAL technologies are slightly more risky; some engineers in FTS walked this path and will share knowledge and experiences.
- ASSESS — Technologies that are promising and have clear potential value-add for us that we test in PoCs; technologies worth to invest some research and prototyping efforts in to see if it has impact. ASSESS technologies have higher risks; they are often brand new and highly unproven in the organization. You will find some engineers that have knowledge in the technology and promote it, you may even find teams that have started a prototyping effort. ASSES technologies can be never adopted depending on the results from Proofs of Concept.
- HOLD — What we used in the past and we should not use anymore for any reason. Technologies not recommended to be used for new projects. HOLD technologies should not be used for new projects, but usually can be continued for existing projects with a specific deadline for replacement.
The FTS Software Tech Radar is one of the pieces with information from the FTS Technology Landscape. Engineering teams can use it to be aware about our needs regarding training, skill sets, evolution, etc; it provides a platform to share knowledge and experience in technologies, to reflect on technology decisions and continuously evolve our Technology Landscape reflected on common platforms. Based on the pioneering work of ThoughtWorks, the FTS Software TechRadar sets out the changes in technologies that are interesting in software development — changes that we think our engineering teams should pay attention to and consider using in their projects.
The Technological Landscape will count on 4 main pieces:
- RoadMap for technologies (made from the information in the TechRadar as a plan for improvement and evolution)
- Proofs of Concept Plan (according to proposed technologies)
- Training plan
The architectural team in FTS will update the TechRadar with information from the different projects and activities.