Overcoming Common DevOps Pitfalls: Practical Strategies from DevOpsDays 2018

Introduction

The content is based on a joint presentation by senior DevOps coaches Liu Zheng and Zhang Le at DevOpsDays 2018 Beijing, titled “How to Challenge the DevOps Practice Journey.” The speakers introduced themselves and explained that the talk would explore how enterprises can start a DevOps transformation, the difficulties and misconceptions they may encounter, and how to measure progress.

Speaker Profiles

Liu Zheng (Martin) – Senior Architect at Nutanix, translator of “DevOps Practice Guide,” core organizer of DevOpsDays China, EXIN DevOps Master and Professional instructor.

Zhang Le – Senior Solution Architect in JD.com’s R&D Efficiency Department, former senior agile coach at Baidu, DevOps and continuous delivery expert, core organizer of DevOpsDays China.

Key Challenges and Misconceptions

Challenge 1: DevOps is only suitable for internet companies.

Both speakers argued that while internet firms often have the right “genes,” traditional enterprises can also succeed by evolving their architecture and culture, as illustrated by examples from Google, Amazon, and others.

Challenge 2: High transformation cost and tool procurement.

Liu shared a story from “The Phoenix Project” to emphasize that tools must add value to the value‑stream, not just be purchased for their own sake.

Challenge 3: Large‑scale organizational restructuring is required.

Zhang explained two team models—functional (slow, hand‑off heavy) and market‑oriented (cross‑functional, fast). Restructuring is not the only path; a matrix or self‑service platform can achieve DevOps benefits without changing the org chart.

Challenge 4: Predictable pitfalls.

The speakers highlighted the need for a learning mindset and continuous experimentation.

Challenge 5: Blindly copying other companies’ paths.

They warned against one‑size‑fits‑all approaches and advocated tailoring to each organization’s context.

DevOps Transformation Framework

The speakers proposed a three‑step DevOps workflow principle:

Flow principle – ensure work moves smoothly from left to right.

Feedback principle – create rapid, rich feedback loops.

Continuous learning – keep iterating and improving.

They then outlined two practical roadmaps.

Method 1: “DevOps Practice Guide” Incremental Path

1. Choose a value‑stream (greenfield vs. brownfield). 2. Visualize the value‑stream to identify waste and bottlenecks. 3. Build appropriate teams and architecture (market‑oriented, cross‑functional). 4. Fuse development and operations.

Method 2: Lean‑Thinking Action Plan

Key steps include finding transformation champions, creating a sense of crisis, aligning organization structure with value‑stream, and co‑evolving with partners.

Case Studies

A DevOps toolchain case demonstrated end‑to‑end continuous delivery using open‑source tools, visual Kanban boards, automated testing, and deployment pipelines.

A US insurance company (National Wide) adopted four parallel practices (Agile, Lean, CMMI, DevOps) and measured all value‑streams by a “lead‑time” metric, supported by a mature internal consulting team.

Assessing DevOps Maturity

The speakers discussed the difficulty of a universal maturity model because of industry‑specific constraints and rapid technology change. They suggested focusing on business‑impact metrics rather than static practice checklists.

Continuous Learning & Improvement

Both speakers emphasized scientific thinking, referencing Toyota Kata and the “Accelerate” book’s capability model. They encouraged small, fast experiments and iterative learning.

Conclusion

The talk summarized DevOps challenges, offered practical methods, suggested measurement approaches, and stressed the importance of ongoing learning. Resources such as a 40 k‑word DevOps mind‑map and future online workshops were announced.