Skip to main content

Technology Radar

What is the Technology Radar?

The Technology Radar provides an overview of current technologies that we believe everyone in our teams should be aware of.

Items are categorized into four categories:

  • Techniques This area covers processes, methodologies, and best practices that guide how your teams work. It can include agile methods, automation practices, testing strategies, and architectural approaches.

  • Tools This area includes specific software tools that support development, testing, deployment, and monitoring of applications. They often enhance productivity and ensure code quality

  • Platforms The category encompasses the infrastructure and runtime environments that support applications. It includes both cloud and on-premises platforms, as well as database systems, application servers, and container orchestration tools.

  • Languages & Frameworks This category lists programming languages, libraries, and frameworks that are available or recommended for specific types of applications. These may vary based on team expertise and specific project needs.

What is the purpose?

Its purpose is to guide and inspire daily work, offer valuable information, and provide a high-level perspective to help make more informed decisions.

Each item is categorized into one of these adoption levels:

  • Assess Technologies that are new to the team or organization and show potential. They’re not in active experimentation yet but are worth exploring to see if they might bring value. This stage encourages awareness and initial consideration without any commitment.

  • Trial Technologies that have moved beyond initial discovery and are undergoing deeper investigation. In this phase, a team might run a small prototype or conduct training to better understand the technology's pros, cons, and fit within the organization.

  • Adopt Technologies that have proven their value and reliability through experience and testing. They’re recommended for production use and have likely become a preferred option within the organization.

  • Avoid Technologies to avoid for the time being, either due to maturity issues or lack of alignment with organizational needs. Teams should steer clear of these technologies for current projects, though they could be re-evaluated if they improve significantly or if requirements shift.