0 views collected around this technical thread.
This article examines common misconceptions in evaluating testing performance, presents a comprehensive "Team Quality Capability Checklist" covering ten essential capabilities, and explains why building these capabilities is crucial for delivering high‑quality software while enhancing team experience and effectiveness.
This article examines how fragmented metrics and local optimizations can harm overall software quality, discussing the bug‑vs‑feature debate, various measurement approaches, and the importance of viewing quality as a collective team capability rather than an individual or departmental responsibility.
This article presents a comprehensive framework for enhancing engineering efficiency and governance in agile delivery, outlining purpose‑driven goals, a golden‑triangle of best practices, metrics, and capabilities, and practical steps for implementation and continuous improvement.
The article explains why software project timelines often slip, introduces the 90% rule, and outlines practical methods—such as thorough requirement analysis, reliable technical design, team capability assessment, handling legacy systems, and accounting for external dependencies—to improve the accuracy of effort estimation.
This article outlines the five key dimensions—organizational structure, agile process, culture, team capability, and technology—of R&D transformation, explaining their principles, common challenges, and practical practices for building high‑efficiency development teams in the financial industry.
The article uses a bus‑schedule analogy to illustrate how long release intervals and frequent hotfixes frustrate customers, then proposes shorter release cycles through better iteration planning, demand splitting, stronger development capability, and robust testing to achieve continuous, rapid delivery.