How a Chinese Telecom Firm Reached Top‑Tier DevOps Maturity – Key Lessons
An interview with China Mobile Suzhou's chief scientist reveals how their "China Mobile Sentiment" project achieved a Level‑3 DevOps continuous delivery assessment, boosting delivery speed, release success, and operational confidence while outlining future scaling plans.
Editor’s note: Standardization and tooling empower tech companies; DevOps standards and continuous delivery pipelines boost software development efficiency.
On March 25, 2021, the China Academy of Information and Communications Technology (CAICT) and partners held the fifth “DevOps Enables Enterprise Digital Transformation” online event.
During the event, CAICT announced the 11th batch of DevOps standard continuous delivery assessment results. China Mobile Suzhou Software Technology Co., Ltd. (China Mobile Software) passed the Level‑3 continuous delivery evaluation, a leading domestic level.
Q: Please introduce your company and the evaluated project.
Qian Ling, Chief Scientist, explained that the company is the R&D center of China Mobile in Suzhou, transformed in 2019 to an operation‑oriented unit running the public “Mobile Cloud”. The evaluated project, “China Mobile Sentiment”, collects online data, performs cleaning, governance, AI analysis, and delivers intelligence to users.
Q: How did you feel about achieving Level‑3?
He expressed excitement, noting the difference between CMMI and DevOps assessments, emphasizing tool‑based, executable processes and the effort required to meet the standards.
Q: Why did you join the DevOps assessment?
Two reasons: the project already adopted DevOps practices, and after the 2019 “cloud transformation”, the number of cloud products grew dramatically, requiring a benchmark project to demonstrate best practices.
Q: What benefits did the assessment bring?
The assessment clarified a roadmap to achieve a Level‑3 or higher toolchain, boosted confidence, and provided a reusable template for other teams, improving agility and quality.
Q: Which metrics show the improvement?
Key indicators include: demand delivery cycle reduced to 11 days (vs. 60‑141 days for other products); release success rate above 95% (vs. 60‑70%); red‑light incident resolution under 15 minutes; test pipeline execution time 7 minutes; and progressive reduction of technical debt.
Q: What are the distinctive features of your IT system?
The company built a configurable management system integrating commercial, open‑source, and self‑developed tools, offering high openness and extensibility for various scenarios.
Q: Was the assessment process smooth?
Overall it was smooth, but meeting the comprehensive Level‑3 requirements required closing gaps in data analysis and reporting capabilities, prompting simultaneous system upgrades and staff training.
Q: What are the next steps?
They plan to expand the DevOps model across more than 200 cloud products, introduce blue‑green and gray‑release strategies, and continue architecture improvements throughout 2021.
Q: How do you view the future of DevOps?
DevOps is a valuable tool that must be adapted to each organization’s culture and structure; broader case studies and guidelines are needed to help diverse enterprises benefit.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Efficient Ops
This public account is maintained by Xiaotianguo and friends, regularly publishing widely-read original technical articles. We focus on operations transformation and accompany you throughout your operations career, growing together happily.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.