The article outlines a practical 7‑step code‑review SOP that leverages IDE static analysis, AI assistance, impact analysis, unit‑test validation, production data checks, non‑functional evaluations, and business‑exception safeguards, enabling banking‑IT teams to achieve two years of zero production incidents.
The article examines why test engineers often end up acting as de‑facto customer‑service agents, outlines three structural reasons and typical symptoms, and offers practical questions and strategies to shift from reactive firefighting to building sustainable, replaceable processes.
This article explains why many factories suffer from blind, fragmented processes, then shows how to design six concrete supply‑chain monitoring dashboards—covering procurement, inventory, production, order delivery, finance, and overall management—to achieve real‑time visibility, clear responsibility, and proactive control.
A software team discovered that Scrum’s ceremonies and story‑point focus were masking weeks of unfinished work, so they switched to Kanban with WIP limits and flow metrics, ran a simple JavaScript simulation, and measured dramatic improvements in cycle time, delivery volume, and team morale.
This article explains how a ultra‑lightweight project‑management tool built with Feishu bots and Coze transforms manual, memory‑based to‑do lists into dynamic, rule‑driven workflows, detailing the problem, design principles, three‑layer architecture, implementation steps, and real‑world impact on testing teams.
A software engineer recounts three major mistakes—from accidentally deleting thousands of F5 URLs to leaking code externally and being laid off during COVID—highlighting how operational oversights, poor process controls, and personal resilience shape professional growth and underscore the value of empathy and systematic safeguards.
This article explains how QA professionals can transform from passive validators into proactive risk forecasters by strategically acquiring, organizing, and sharing information throughout the software development lifecycle, boosting testing depth, collaboration, and overall product quality.
Even without coding skills, test engineers can manage customer complaints professionally by listening empathetically, gathering key data, using non‑technical tools to pinpoint issues, communicating clearly with developers, and conducting post‑mortems to prevent recurrence.
The article analyzes why basic functional testing roles are oversupplied, presents three concrete strategies—niche specialization, quantifiable value creation, and strategic networking—to stand out, and advises a rational career pivot when progress stalls, all backed by real‑world examples and hiring data.
This article explains what technical debt is, why it harms software projects, and presents a comprehensive framework—including identification, prioritization, remediation, monitoring, and continuous improvement—to manage and reduce technical debt, ultimately boosting security, development speed, and innovation.
This article explains how to make QA proactive by mastering pre‑release collective testing, daily monitoring of core interfaces, immersive online inspections, and a closed‑loop post‑incident review, turning routine checks into a powerful, collaborative quality shield.
The article analyzes McKinsey’s latest research on why organizational restructuring alone fails to sustain productivity gains and outlines a four‑step framework—diagnosing workflow bottlenecks, removing redundancies, synchronizing information, and leveraging AI—to streamline processes, break departmental silos, and unlock lasting value.
Huawei’s project‑management model transforms the company from a functional to a project‑centric organization through a comprehensive system of policies, processes, tools, and culture, detailing its three‑layer governance, maturity levels, and the six‑stage lifecycle that drives commercial value and strategic execution.
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 analyzes why overly complex R&D metrics often hinder productivity, proposes aligning indicators with company strategy and culture, and illustrates the approach with TDengine’s single‑KPI model and a three‑metric framework for banking, while also detailing the “Everything as Code” practices that boost development speed and quality.
The article outlines a step‑by‑step approach for handling production incidents in fintech, emphasizing direct communication, rapid impact assessment, temporary business work‑arounds, and technical fixes, followed by a broader review of development processes to prevent future issues.
The article argues that cultivating a strong engineering culture—through shared values, clear processes, automation, altruistic collaboration, and continuous self‑improvement—empowers programmers to remain reliable and productive despite uncertainty, boosting the odds of sustained success while acknowledging that culture is only one of several critical factors.
Building system stability requires quantifying risk through formulas, confronting challenges like low short‑term value and resource competition, and implementing a consensus‑driven framework that sets clear goals, cultivates awareness, enforces safety standards, ensures emergency response, conducts routine inspections, and applies sound architecture governance to continuously reduce inherent and change‑related risks.
The article explains why developers must combine deep business understanding with AI tools, outlines a three‑layer domain model (core, generic, supporting), debunks common misconceptions, and provides a step‑by‑step methodology for mastering banking business concepts to boost ROI and career resilience.
This article describes how a data construction platform combined with an API integration solution and self‑service verification model dramatically reduced testing cycles and manual effort, enabling third‑party partners to onboard faster while standardizing processes for future projects.
The article examines a real production incident, highlights how a proactive manager turned the crisis into a learning opportunity by soothing customers, reporting transparently, and then systematically analyzing team processes and management responsibilities to prevent future issues, illustrating the broader principle that danger and opportunity coexist.
This guide outlines a complete workflow for handling software bugs—from immediate reporting and triage through impact assessment, resolution strategies, post‑incident analysis, and long‑term process, testing, and organizational improvements—to ensure stable releases and continuous quality enhancement.
Facing a critical production deadline, the author shares a three‑step communication and process framework—empathic praise, collaborative brainstorming for an interface delivery review, and reflective design improvement—to strengthen middle‑platform team cohesion and establish robust API governance practices.
This article outlines a practical, end‑to‑end quality assurance framework for large, cross‑department projects, detailing actionable steps and best practices for each phase—from requirement analysis and design through integration, testing, deployment, and post‑release monitoring—to help QA leads proactively identify and mitigate risks.
Effective requirement quality—clear, complete, measurable, consistent, and feasible—significantly reduces rework, accelerates development, optimizes resource allocation, and enhances team collaboration; the article outlines key quality attributes, measurement indicators, influencing factors, improvement methods, and real-world case studies demonstrating their impact on project success.
The article examines Amazon's Correction of Errors (COE) process, presenting both supportive and critical SDE perspectives, and discusses whether detailed post‑incident documentation truly improves engineering practices or merely adds bureaucratic overhead.
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.
This article explains the concept of quality operations, outlines its main components, lists essential quality‑operation KPIs, describes how to collect and analyze KPI data, and shows how to align KPI metrics with overall business strategy.
Software development efficiency faces multiple challenges such as slow business growth versus high technical labor costs, high customer expectations versus limited delivery capacity, excessive product manager demands, and legacy system debt, and improving it requires enhancing team skills, communication, process quality, and management practices.
This article presents eight core IPD measurement indicators—covering project basics, size, milestones, workload, requirement stability, defects, and overall analysis—illustrated with visual charts and accompanied by recommended reading on development efficiency and quality standards.
This article explains the concept of retrospectives, identifies common misconceptions, distinguishes them from ordinary summaries, outlines why they are essential for personal and team growth, and provides a detailed, step‑by‑step framework for conducting both individual and team retrospectives in a disciplined, improvement‑focused manner.
The article presents a comprehensive framework for evaluating engineering productivity by separating efficiency (speed and quality) from effectiveness (usability), reviewing academic literature, interviewing Google engineers, and proposing four interrelated types of software quality—process, code, system, and product—along with practical measurement challenges and recommendations for technical leaders.
This article explores the history of Engineering Productivity (EP) from its Google origins, examines how Chinese companies have adopted EP practices, discusses future development trends including AI‑driven tooling, and offers practical advice on metrics, team improvement, and career transitions.
This guide outlines a comprehensive learning path for aspiring software quality engineers, covering goal setting, theoretical study, hands‑on practice, industry trend tracking, case analysis, tool mastery, community involvement, and continuous self‑assessment to build a solid QA career.
This article shares practical steps and key insights for conducting a project test retrospective, covering purpose clarification, mindset adjustment, documentation preparation, meeting facilitation, feedback collection, and lessons learned, illustrated with examples from the KE offline rendering cloud map project to help teams improve quality processes.
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 outlines a structured approach for R&D managers to lead quarterly retrospective meetings by asking four key question groups—result, process, gap, and improvement—each broken down into specific sub‑questions that help uncover issues, analyze causes, and define actionable plans for continuous performance enhancement.
This article explains how QA evolves from basic functional testing to holistic quality assurance, outlines the differences between testing and quality, and provides detailed, stage‑specific strategies—including process, automation, monitoring, and risk management—to build sustainable quality systems for both mature iterative and short‑cycle business models.
This article explores the concept of R&D efficiency, outlines its goals, debunks common misconceptions, and presents a practical framework—including practice, platform, and measurement components—supported by visual models to help technology organizations improve delivery speed, quality, reliability, and sustainability.
The article analyzes why test scenarios often lack full coverage, identifying both subjective causes such as carelessness and insufficient knowledge, and objective factors like tight schedules and low‑fidelity test environments, then proposes pre‑, during‑, and post‑testing strategies to enhance coverage.
A seasoned test developer shares a decade‑long journey, detailing the evolution from functional testing to test automation, the construction of a comprehensive quality assurance system, practical tools for repetitive problems, and personal reflections on perseverance, collaboration, and continuous learning.
The article outlines a practical, stage‑by‑stage approach to establishing and evolving a quality‑assurance system—from early product inception to decline—highlighting which testing activities, tools, and cross‑team collaborations are most valuable at each phase.
The article explains how business and domain modeling—using UML diagrams, RUP‑based workflows, and DDD principles—help engineers bridge the gap between business problems and technical solutions, enabling clearer requirements, stakeholder alignment, and improved system design across complex industries such as finance, logistics, and e‑commerce.
The article outlines a practical roadmap for quality assurance across the software lifecycle, highlighting the pivotal roles of clear requirements, sound technical implementation, risk and project management, and measurable cost metrics, while stressing the need for solid processes and infrastructure.
This guide details how the Big Data Real‑Time Platform department organized a Bug Bash activity to train new staff, enhance cross‑product knowledge, improve product quality, and strengthen team collaboration through structured preparation, execution, and post‑event analysis.
This article presents a comprehensive test summary of a six‑month project involving eight applications, detailing test objectives, planning, execution cycles, case counts, defect statistics, quality metrics, and management lessons that together delivered a 99.9% transaction pass rate and valuable insights for test leaders.
This article examines why many testing teams skip bug root‑cause analysis, outlines typical scenarios where such analysis is needed, and presents a practical four‑step method—including recording, cause marking, role attribution, and improvement planning—to enhance software quality and team efficiency.
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 article reviews JD.com’s automation testing framework, explores how Conway’s Law and organizational culture affect software quality, presents a coupon‑system redesign case, and offers practical guidance on metrics, team cohesion, and probabilistic effort estimation for high‑quality delivery.
This article argues that systematic documentation dramatically improves productivity, reduces unnecessary meetings, and builds a sustainable knowledge culture in startups, offering practical advice on tools, templates, and team habits to make documentation a core engineering practice.
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 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.
The article compares a large, waterfall‑style, client‑driven project (Project A) with a business‑centric, agile project (Project B), highlighting how agile practices such as continuous collaboration, iterative testing, and value‑driven development lead to higher software quality, faster delivery, and happier teams.
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 article outlines a three‑level problem‑solving methodology—emergency response, deep analysis, and pursuit of excellence—providing technical managers with concrete steps, communication templates, and real‑world SaaS examples to boost team performance and drive continuous improvement.
This guide outlines twenty essential steps for creating an efficient software testing team, covering goal definition, strategy planning, hiring, process and tool setup, training, communication, continuous improvement, environment management, automation, agile practices, documentation, and fostering a culture of learning and collaboration.
This article introduces essential testing knowledge for beginners, covering test case design methods, execution techniques, process standardization, efficiency improvements, and communication skills, providing practical guidance and templates to help new testers quickly become effective contributors in software quality assurance.
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.
The article defines R&D efficiency as delivering higher‑quality, faster value, breaks it into doing the right work, doing it correctly, and ensuring sustainable delivery, then presents a GQM‑driven framework and case studies on testing staff, code review, and process bottlenecks, and outlines a digital decision‑making platform that automates data collection, modeling, and actionable reporting.
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 examines the challenges of complex, multi‑person workflow tasks, proposes a five‑element task model, and presents a step‑by‑step research method—including investigation, flowcharting, decomposition, experience and efficiency studies—illustrated with a pre‑employment case to reveal optimization opportunities.
Drawing on three years of product‑team experience, the article outlines how OKR tracking evolved through a “Do‑Not” start, process consolidation, and an information‑driven timeline, emphasizing weekly summaries, bi‑weekly meetings, monthly celebrations, quarterly reviews, a lightweight “callme” tool, and core principles of transparency, positive incentives, and a happy team culture, while urging each team to tailor its own rhythm for continuous improvement.
The article examines how testers often become scapegoats in software projects, detailing three layers of blame—from missed delivery schedules and unmet quality expectations to emergency releases—while arguing that underlying architectural and design flaws, not testing, are the true sources of product defects.
This article explores the unique challenges of technical project management in internet companies, outlines the origins of tech projects, defines the critical roles of project manager and technical lead, and presents a comprehensive process—including goal clarification, KF thinking, and structured phases—to ensure successful delivery.
The article advises teams to adopt OKR gradually with minimal friction, using simple, phase‑appropriate tools instead of heavyweight solutions, while steering clear of tool‑centric traps, bureaucratic formalism, and short‑termism, and focusing on transparent formulation, regular tracking, and reflective review to embed OKR habitually.
In this expert round‑table, leaders from WeBank, Tencent and Kuaishou share practical insights on applying measurement frameworks such as GQM, value‑flow management and DevOps metrics to guide development behavior, improve quality and efficiency, and avoid common pitfalls in software R&D.
This article explains what maturity models are, why they matter for evaluating and improving organizational processes, reviews common business process maturity models (BPMM) and their limitations, introduces the Capability Maturity Model (CMM) and the Agile ISO Maturity Model (AIMM), and offers guidance on selecting and applying a suitable model.
The 2022 GOITI IT Technology Leadership Awards highlighted Zhongyuan Bank’s EPG Process Improvement Team, whose dual‑mode, multi‑speed delivery framework, online management platform, intelligent performance metrics, and data‑driven improvement loop have transformed the bank’s R&D efficiency, accelerated product cycles, and earned multiple industry certifications.
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.
This article guides R&D team leaders through the mindset, stages, implementation steps, application patterns, common challenges, and future directions for adopting low‑code platforms to reduce costs, improve efficiency, and solve specific business problems.
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.
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.
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.
This document outlines a detailed Service Level Agreement (SLA) framework covering quality service standards, management processes, testing capabilities, tool support, resource management, measurement systems, risk handling, and continuous improvement to ensure consistent delivery and customer satisfaction across IT operations.
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 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.
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.
This article details the design and implementation of a comprehensive quality assurance system for SDK development, covering background motivations, step‑by‑step methodologies, documentation practices, toolchains, real‑time crash data handling, hardware testing, platform automation, and practical Q&A for startup engineering teams.
The article shares a detailed account of serving as the first test lead for a large middle‑platform project, describing the background challenges, preparation steps, daily test coordination, post‑release reflections, and practical takeaways for improving testing efficiency and cross‑team communication.
The article explains how integrating the four "持" principles from the book "Continuous Delivery 2.0" into daily software development can prevent the recurring problem of late‑night releases by emphasizing minimal work, continuous decomposition, feedback, and ongoing improvement.
The article examines software development efficiency from both human and technical perspectives, highlighting how overlooking human factors leads to failed automation attempts, illustrating the Hawthorne effect through a real experiment, and discussing immutable “physical” laws such as Moore’s law that shape productivity, ultimately offering practical actions to improve R&D performance.
This article outlines eight practical recommendations for boosting R&D efficiency, from tackling pain points and adopting a global perspective to ensuring continuous improvement, avoiding vanity metrics, and embracing a service mindset, emphasizing measurable outcomes and the importance of using the platform yourself.
This article explores the philosophy and practical techniques of failure‑oriented design, covering why anticipating failures is crucial for developers, the organizational and process changes needed, core design principles, and concrete implementations such as multi‑level Redis distributed locks with code examples.
This article shares practical experience of applying the Agile Team Maturity Model (ATMM) to evaluate and improve agile team processes, detailing the model’s evolution, assessment steps, team dialogues, feedback, and lessons learned for effective R&D management.
This article examines how defining and progressively moving the Definition of Done (DoD) within agile feature teams can clarify goals, reduce unfinished work, improve iteration completion and delivery rates, and ultimately increase development throughput through concrete metrics and practical steps.
This article examines how a software team transformed its daily stand‑ups by introducing physical Scrum and Lean Kanban boards, detailing the observed problems, step‑by‑step improvements, measurable outcomes, and future refinements to enhance transparency, focus, and value‑flow.
This article shares CoolHome’s comprehensive SaaS project delivery framework, detailing each phase—from initiation and planning to execution, monitoring, and closure—while highlighting common pitfalls, improvement measures, and practical tips for managing large‑client engagements effectively.
The article presents a data‑driven framework for technical support to boost its autonomous handling ratio, covering knowledge‑base creation, diagnostic tool mastery, standardized issue templates, controlled feedback channels, self‑service infrastructure, detailed analytics, and disciplined retrospectives to reduce developer support time and improve efficiency.
This article examines the challenges of improving research and development efficiency in digital-era enterprises, presents real-world success and failure cases, outlines the roles of business, tool, coaching, and organizational teams, and offers practical do's and don'ts to achieve sustainable, business‑driven efficiency gains.
This article describes how the Auto Home Dealer business unit transformed its software quality process over three years by piloting, scaling, and institutionalizing testing practices, addressing role‑specific challenges, introducing automation, and continuously measuring impact to achieve faster, more reliable releases.
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 article outlines how improving R&D productivity hinges on three essential factors—people, process, and tools—detailing practical insights on cultivating engineering mindset, optimizing workflows, selecting effective tools, establishing robust metrics, and implementing fair assessment methods.
The article reflects on Huawei’s twenty‑plus years of digital transformation, analyzing its guiding philosophy of customer‑centricity, the evolution of its management methods, practical techniques, and supporting tools, and draws lessons for other enterprises navigating continuous change.
By treating postpartum parenting as a structured project—defining kickoff, phases, milestones, daily and weekly task iterations, stakeholder roles, communication protocols, and continuous retrospectives—the author successfully coordinated mother, baby, and family activities during 143 days of maternity leave, achieving all goals and returning to work.
Technical Support teams boost self‑processing rates by building personal knowledge bases, using diagnostic tools, standardizing issue templates, managing feedback channels, creating automation tools, analyzing data trends, and conducting regular post‑mortems, thereby reducing developer support load and increasing overall efficiency.
The article examines historical and modern cases of metric failures, analyzes root causes such as over‑reliance on easy‑to‑collect or single‑dimensional indicators, and offers practical guidance for building multi‑dimensional, automated, and team‑focused measurement systems that truly support software development goals.
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 explains how lean value‑stream analysis uses meaningful metrics such as lead time, process time and percent complete & accurate, outlines a step‑by‑step workflow for mapping and evaluating value streams, and demonstrates the approach with a department‑level case study and radar‑chart analysis.
The article analyzes Huawei’s software development organization, highlighting issues such as separation of architects from coding, multi‑layer management, rigid IPD processes, high communication overhead, inadequate tooling, and talent retention challenges, and proposes practical improvements for faster, higher‑quality delivery.
This article presents a bottom‑up, self‑consistent team management system that categorizes over sixty practices into ten modules across two dimensions, offering actionable insights on time, project, technical, process, institutional, goal, performance, recruitment, talent development, and team building.
