The article examines the circumstances under which a Scrum team might outgrow the framework, discussing the Stacey matrix, evolution of team maturity, key indicators of diminishing Scrum value, and concluding that teams should abandon Scrum when it no longer serves its risk‑reduction and product‑discovery purpose.
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 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.
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.
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.
Effective documentation is a critical, long‑term productivity booster for startups, enabling knowledge sharing, reducing reliance on meetings, mitigating risks, and empowering teams to scale, and this article outlines how technical leaders can build a documentation‑first culture, tools, processes, and habits to achieve it.
This narrative recounts how Zhang Dapeng, after self‑studying Docker and Kubernetes, launched a series of technical sharing sessions that initially failed, prompting his manager to impose a strict review process that ultimately led to superficial compliance, a managerial award, and a reflection on three attitudes toward learning.
This article explains why equipment failures often lead to blame‑shifting between production and maintenance teams, defines clear responsibilities, and outlines a four‑step system—including daily inspections, maintenance scheduling, fault handling, and performance metrics—to achieve coordinated, data‑driven equipment management.
The article outlines China's agile development and DevOps maturity standards, highlights the rapid adoption by major financial institutions such as the Agricultural Bank of China and China Merchants Securities, and details the measurable improvements in delivery speed, quality, and user satisfaction achieved through these practices.
A four‑hour Cloudflare outage was triggered by an unauthorized cable removal during a planned maintenance, compounded by unclear instructions and unlabeled wiring, highlighting the need for better cable management, clear operational procedures, and robust single‑point‑of‑failure mitigation.
This talk explores how ops engineers can achieve continuous professional development by adopting checklist thinking, covering growth drivers, error classification, practical checklist applications, cognitive models, and design principles that turn complex incidents into systematic, repeatable processes.
This article chronicles SF Express’s journey of transforming its IT operations department—from a fragmented, silo‑based structure to a streamlined, DevOps‑driven organization—highlighting the challenges of excessive processes, the five “sins” of traditional ops, the strategic initiatives undertaken, and the lessons learned for achieving efficient, automated, and self‑service infrastructure management.
The article explores why operations professionals often feel exhausted, unrecognized, and low, identifying six systemic shortcomings—lack of a holistic ops framework, unclear positioning, closed mindset, insufficient authority, stagnant improvement, and missing cultural integration—and offers practical guidance to transform these weaknesses into strengths.
This article explores why operations teams must adopt a people‑centric mindset, outlines a three‑layer framework of framework, blood (processes & policies) and interface, and provides practical steps for improving processes, technology, and organization to boost efficiency and employee satisfaction.
By abstracting 86 % of form‑list‑detail scenarios into standardized scene assets and linking them with unified data models, the platform enables no‑code generation of backend pages, cutting development effort fivefold versus source code, boosting overall productivity by 68.6 % while preserving product quality and consistency.
The article shares a test engineer’s seven‑year journey, highlighting four pivotal shifts in testing practice, redefining the engineer’s duties toward helping projects improve quality, quantifying quality metrics, and continuously refining tools and processes to enhance overall product reliability.
This article details how the used‑car technology team at Autohome optimized R&D efficiency through standardized workflows, task decomposition, unified time‑based measurement, rigorous demand review, flexible branching, CI/CD pipelines, and data‑driven metrics, resulting in higher throughput and reduced bug rates.