Login
Register
Operators are turning to DevOps to streamline their software processes and increase agility and innovation when delivering new digital services and products.
By submitting this form, you acknowledge that your contact information, including email address, will be shared with the sponsor, and consent to TM Forum contacting you by phone or email to fulfill your request and to inform you about appropriate products or services.
Sponsored by:
DevOps: Where, why and how?
At its best DevOps bridges the gaps between the design, development, delivery and use of software by a business, in conjunction with changes to culture, processes and technology. Increasingly, communications service providers (CSPs) are making DevOps part of their business and technology transformation strategies. But CSPs’ complex legacy systems and working practices risk marring the success of DevOps initiatives unless they become an integral part of wider transformation programs. CSPs are turning to DevOps to increase agility and make it easier to experiment and innovate rapidly to deliver new digital services and products. Agile approaches to software development have helped IT teams and business stakeholders collaborate more effectively, but a cultural and process divide between development teams and those responsible for operations often persists. DevOps breaks down these barriers by introducing an end-to-end software lifecycle, where all those involved have a responsibility for delivering a working product that meets the needs of customers. This is supported by process changes that enable a continuous flow of software development, integration, testing, delivery and deployment. There are several challenges for CSPs when making this transition, however, including a significant debt of legacy technology, a historically rigid divide between IT and network teams, and the fact that most software is procured from vendors rather than developed in house. CSPs have therefore been relatively slow to adopt DevOps. To date, most of their efforts have focused on customer-facing digital initiatives which tend to be relatively standalone and built on a cloud native architecture from the outset. Read this report to understand:
