This article explains why quality operation is needed for a transaction platform, describes the origin and problems that motivated the Quality Month, outlines a seven‑element operation plan with goals, strategies, resources, data collection, and evaluation, and shares the results and lessons learned.
This article analyzes the challenges of fragmented, high‑volume demand in a trading platform’s QA process and describes how introducing a tiered “no‑test” policy, white‑list and data‑driven operations, and rapid‑response procedures significantly boosted delivery efficiency and raised developers’ quality awareness.
The article outlines the purpose of a Project Management Office (PMO), detailing its functions such as resource coordination, data‑driven decision support, project prioritization, risk reduction, and knowledge‑base creation, and describes the key activities during the PMO’s establishment, standardization, and maturity phases.
The article analyzes why business and development teams often clash over requirements, explains the inherent upper and lower limits of IT production capacity, and proposes practical ways—such as staffing, process optimization, architectural improvements, and demand prioritization—to continuously raise the IT output ceiling while lowering maintenance burdens.
The article analyzes the difficulties of quantifying software R&D efficiency, critiques common measurement methods, proposes two guiding principles—global over local metrics and result over output—and presents a comprehensive set of delivery efficiency, quality, and capability indicators with calculation logic.
The article describes Tubi's three‑month experiment to replace traditional waterfall and rigid sprint models with a flexible Release Train system, outlining the motivations, principles, team roles, tooling choices, successes, and areas needing improvement for a fast‑growing startup.
This article presents a series of agile process‑improvement case studies—including flexible response to change, effective communication, goal‑aligned teams, and robust engineering culture—offering practical guidance for software teams seeking to adopt and sustain agile transformations.
The article explains the concept of closed‑loop thinking, illustrates how it can be applied to software testing through a concrete bug‑handling example, and shows how systematic feedback and reflection improve testing efficiency, knowledge reuse, and personal skill growth.
This article shares several agile process‑improvement case studies—from enhancing team responsiveness and communication to building strong engineering culture—offering practical guidance on establishing visibility, efficient decision‑making, minimizing re‑planning costs, and fostering high‑quality, cross‑functional delivery teams within software development.
This article recounts how Tencent’s advertising team introduced and scaled a rigorous code review process—starting with the Rietveld system, adopting Google C++ coding style, and establishing metrics and ownership—to improve code quality, knowledge sharing, and engineering efficiency across multiple departments.
This article describes Anjuke's R&D efficiency measurement framework, detailing its quality and efficiency metrics across project phases, the data collection and processing architecture, visualization dashboards, and analysis methods used to monitor and improve development productivity, reliability, and continuous delivery.
This article explains how to measure and improve R&D efficiency by defining core factors, building data‑driven analysis models, presenting practical case studies on human productivity, code‑review processes and workflow bottlenecks, and describing the technical architecture of a digital platform that turns metrics into actionable decisions.
This document outlines the background, inspection methods, focus areas, schedule, responsibilities, and outcomes of a regular business inspection process designed to improve quality, user experience, and NPS by involving developers, QA, and product teams in systematic functional, page, and interaction reviews.
This article analyzes the challenges of traditional system load testing, proposes an iterative testing workflow that enhances service and environment stability, reduces manpower and timeliness costs, aligns testing with business needs, and outlines the evolution of a full‑process testing model with practical feedback.
This article outlines how QA can proactively join technical design reviews, detailing the required documentation, preparation steps, thinking methods, impact assessment, and testability improvements to ensure higher delivery quality and better collaboration among product, development, and testing teams.
This article explains how to improve overall delivery efficiency by systematically breaking down testing tasks, setting realistic schedules based on clear goals, preparation steps, granular time estimates, dependency considerations, and post‑execution reviews, while emphasizing a target testing effort not exceeding half of development time.
This article outlines a comprehensive A/B testing workflow, covering historical issues, business test process improvements, detailed implementation steps, SQL validation scripts, data verification in analytics platforms, and practical notes to ensure accurate experiment data collection and analysis.
This guide outlines common tester‑developer interaction scenarios, highlights typical mistakes, and provides step‑by‑step best‑practice responses to improve bug reporting, collaboration, and overall software quality assurance processes.
This article shares ZhaiZhai's data‑driven approach to process improvement, detailing how development self‑testing and code‑review practices were introduced, measured, and refined using PDCA cycles to boost quality, efficiency, and team morale across multiple teams.
This article shares practical insights on QA versus QC, essential skills for becoming a qualified QA, demand analysis, test case creation, test‑left and test‑right shifts, bug analysis using the 5‑Why method, automation tools, and a personal tool‑development case, all aimed at improving game testing professionalism.