Case study

Communication Management Platform


  • The goal of the telecom platform is to manage all customer-related interactions, like creating contracts and subscriptions, agreements, invoices, planning, and hardware production (phones, etc.)
  • Our approach was first to stabilize the existing application, create a CI/CD environment, and adapt the whole development process to this new infrastructure.

Java, JavaEE, Kubernetes, Docker, Elasticsearch, Kafka, OracleDB, Jenkins, SonarQube, Spring Boot


Software Development, Software Architecture, DevOps, Manual/ Automated Testing, Product Management – Product Owners, Development Process Org. – Scrum Masters


Team Size

5+ Years





The end client is a global player in the telecom industry. The problems it was facing with its current management platform were related to downtime and performance issues due to legacy systems. At the same time, the client started an internal digital transformation process and moved from a waterfall-type company to an AGILE company with all internal processes and projects.

Our approach was to stabilize the existing application, create a CI/CD environment and adopt this infrastructure for all projects we were involved in. The next step was transformation of the pre-existing monolithic architecture into a micro-services infrastructure while at the same time continuing to develop new product functionalities. The cloud deployment was accomplished using the client’s enterprise solution.


Before being handed over to our team, the product had a bi-annual release cycle; multiple high and blocker incidents were present, as well as several huge performance issues. The application was a legacy system developed over multiple years, and it was a conglomerate of technologies and frameworks that caused the system to be very rigid and unstable. We received the source code on USB drives together with dependencies. As a result, the code was not even easy to compile. Our first mission was to make the source code compilable and to create the first build and deploy it into production.

On the way, the client adopted SAFe as the project methodology, and in the transition period, we planned the first PI Planning pilot. We worked in parallel streams of development: system architecture and business feature development.

With our Product Owners and Scrum Masters, most of the product concept definitions and team/product organization aspects were well-received and successfully implemented, which transformed the collaboration into two long-term projects.

Client Benefits

Performance Improvements

We placed 30 microservices in production and automated the code quality checks, leading to 0 blocker issues.

Extendable Architecture

An easily maintainable and extendable architecture (microservices architecture) and modern technologies (Kafka, Spring Boot) lowering the overall maintenance costs.


Teams and products aligned with the client’s vision, producing the desired results with reduced involvement and time from the client side.