The article explains why agile transformations often fail when teams focus only on isolated Scrum practices, and proposes that true improvement requires synchronizing the process chain, organizational structure chain, and tool chain to achieve smoother end‑to‑end business delivery.
This article recounts a real-world incident where a junior engineer mistakenly uploaded production data to a pre‑release environment, analyzes the root causes, outlines concrete process improvements, and highlights broader lessons on risk‑aware development and the importance of holistic business‑logic security.
This article explores various innovative metric visualizations and practices for agile teams, distinguishing process and value metrics, emphasizing accurate data collection, and offering numerous chart examples to deepen insight and drive continuous improvement.
The article explains how a Scrum master uses the ORID (Objective‑Reflective‑Interpretive‑Decisional) framework to structure a sprint retrospective, detailing preparation, four discussion rounds, voting on improvement actions, and post‑meeting follow‑up to enhance team collaboration and process quality.
This case study describes how the Theory of Constraints' five-step drum‑buffer‑rope method was applied to Microsoft’s XIT maintenance engineering team, transforming a severely overloaded workflow into a high‑throughput operation, achieving a 155% productivity boost, reducing lead times to two weeks, and eliminating the bottleneck without adding resources.
This article explains Huawei's implementation of quality traceability, describing its concept, purpose, the FRACAS system, root‑cause analysis methods such as 5‑Why, practical steps, case studies, and how it supports continuous improvement in R&D and operational processes.
This article explains how agile teams can run productive retrospective meetings to capture successes, identify problems, and implement actionable improvements, sharing real‑world experiences, common pitfalls, and concrete guidelines for moderating, prioritizing, and tracking outcomes across iterations.
The article explains why teams should focus on delivering value rather than isolated features, defines the concept of a value stream in software development, outlines its four essential components, and describes how to visualize and improve it through a collaborative DevOps Transform Canvas workshop.
Lean Thinking, originating from Japan's Toyota Production System, evolved from post‑war mass production to a comprehensive management philosophy that emphasizes waste elimination, value creation, continuous improvement, and adaptable processes across manufacturing and service industries, influencing modern practices such as Agile, DevOps, and Kanban.
This article outlines how a major state‑owned commercial bank designed and implemented a DevOps framework—including goals, architecture, the three main pillars of tools, processes, and standards—and shares practical insights, maturity assessment methods, and Q&A for large‑scale financial institutions.
The Q Team from Xiaomi’s Information Technology Department documented a six‑step agile transformation that defined roles, built JIRA boards, aligned iteration calendars, integrated product and testing, shifted quality activities upstream, and established daily cross‑city video syncs to improve overall quality management and team efficiency.
The article details how a supply‑chain contract‑manufacturing team, guided by Agile mentor Wang Lijie, assessed its current practices, organized project requirements, established iterative workflows, held daily stand‑ups and retrospectives, and outlined future steps such as continuous integration, automated testing, and BDD to achieve a more flexible, value‑driven development process.
The author reflects on a recent emergency department visit, highlighting excessive queuing and fragmented steps, and draws parallels to agile and DevOps transformations, emphasizing the need for customer‑centric process redesign and value‑stream mapping to reduce waste and improve efficiency.
The article reflects on the 2019 Scaled Agile Spring Summit discussion of the "Quality is low" problem, analyzing its causes, distinguishing internal and external quality, exposing common measurement pitfalls, and proposing a process‑driven Build‑In‑Quality approach supported by agile, DevOps, and metric frameworks.
The article reflects on Huawei’s public letter urging a comprehensive upgrade of software‑engineering practices, explaining concepts such as IPD, the project‑management triple constraint, architecture, technical debt, security, and cultural change, while emphasizing the need for trustworthy, high‑quality software development.
This article recounts a real‑world Kanban board improvement performed by a software development team, describing the initial problems, a 15‑minute, four‑step redesign process, and the resulting clearer task visibility, better WIP control, and stronger team alignment.
This article presents detailed English summaries of Scenarios 8 through 15 from The Phoenix Project, outlining roles, events, key learnings, and actionable steps that illustrate DevOps principles, bottleneck management, lean operations, and the integration of IT with business objectives.
The article uses a bicycle analogy to explain why teams should first faithfully follow Scrum, then experiment with modifications only after sufficient practice, recommending a 100‑hour disciplined trial before deciding to trim the framework.
This article explains how to control work‑in‑progress using the lake‑water‑rock metaphor, outlines realistic and useful principles for setting WIP limits, describes common limiting methods such as swim‑lane caps, stage caps, and personal caps, and offers practical ways to determine initial limit values.
The article explains the four‑hold principles from Continuous Delivery 2.0—doing less, continuously decomposing work, constantly gathering feedback, and pursuing ongoing improvement—and shows how applying them can eliminate late‑night release cycles, improve DevOps feedback loops, and strengthen R&D management in software projects.