ect logo white

Continuous
Co-Development with CSPs
(Telco Tech EP03)

Estimated Reading Time: 3 Minutes
On our third episode of Telco Tech, our host Diego Vivas, ECT's Director Product Management and Tech Evangelist, talks with Wolfgang Huber, deputy CTO, about how co-development between CSPs and ECT works.
Below is a transcript of the episode, edited for readability. To watch the full video, click here or go to Videos and Webinars.


Hi, I'm Diego with ECT. And welcome back to our Telco Tech video series. Today we'll be discussing about co-development, a topic very close to my role at ECT. And for this, we have a very special guest. Wolfgang, thank you for joining us. Why don't we start then telling our audience who you are and what you do at ECT.
My name is Wolfgang Huber. I've been a member of the ECT company for more than 17 years now and take the role of the deputy CTO. My responsibilities include the different telecommunications protocol stacks, the application layer, and the business logic implementation throughout our different development squads.
Okay, so… development squads. We have the topic here today of co-development, right? So it's very hard to hide that this reputation about telecoms networks – and also the implementation of services in those networks –tends to be that [they are] slow and cumbersome. Can you tell us why is that?
Well, I think this reputation is still based on the old waterfall model where the specification was at the very beginning. The next step was a long development process with all the line coding and no questioning of specification parts. After a long time, when the development process finished, you had the first view on the product. At that point, you saw all the unusable concepts and maybe some features were obsolete. Then it started again from the beginning in a long lasting circle.
Okay, but that's not the case anymore, at the very least. So there's low code now and we have Telecoms Low-Code with our Telecoms Low-Code Application Platform, or T-LCAP. So can you explain then what has changed and what's new?
Our T-LCAP is designed to support agile methodology. We and our customer work together in several two-week sprints. Business outcomes are visible after each product increments where people can do A/B testing to get the best business results. In that way, our customers can react quickly to new requirements and requests. With our low-code/no-code programming solution, our customers can produce a lot of code in high quality quite easily.
That sounds a bit challenging. So producing a lot of code, producing applications… Do they have to do it on their own… and even from scratch?
No, of course not. We provide ready-to-use apps which can be changed quite easily with our graphical editors. We provide fundamental modules – or package business capabilities – which can be integrated in all the different services. With little or no coding, you can individualize your services for your businesses. Besides that, we offer a co-development program where dedicated squads work hand in hand with our customers to bring their ideas to life.
Okay. Bringing their ideas to life, that sounds a very good advantage. Also, of course, everything what you said about being able to test a feature or even a product prior to any launch decision and without any dedicated budget or investment needed. So that sounds very promising.
We have a lot to tell right about collaboration and co-development. We will do that in the following [videos of our] series and I would like to thank you for being here and I would like to invite our audience to stay tuned. We will discuss about our R&D ecosystem in future videos and also about how we collaborate with CSPs around the world around our Joint Agile Product Development.
For today, thank you, and thanks to you. See you next time. Bye.
Author:
ECT Editorial Team
ebook cover bringing low code to telecoms

Download the E-book

The Promise of Telecoms Low Code

This e-book will change the way you see telecoms service creation.

exit-intent-ebook