Agile Transformation and Maturity Diagnosis Practices in JD Shopping App

JD.com began its e‑commerce journey in 2004 and, by 2019, its Shopping App had grown to over 70 product lines, handling more than 300 release demands per version and accounting for 90% of daily orders, supported by a team that expanded from a few dozen to over a thousand members.

To cope with high business complexity, rapid change, large‑scale distributed teams, and strong inter‑system coupling, JD implemented an agile transformation that reduced delivery cycles by 10%, improved collaboration efficiency by 20%, and increased product quality by 30%.

The transformation followed a roadmap (see Fig. 1) that started with comprehensive research, proceeded through organizational adjustment, agile method introduction, diagnosis and measurement, benchmark team creation, and continuous improvement, aligning with project management phases of initiation, planning, execution, monitoring, and closing.

Key to the effort was the development of an agile maturity diagnosis method, comprising diagnostic dimensions, items, and levels. The model (Fig. 2‑5) defines dimensions such as “Management Practices” with items like “Communication & Collaboration,” each mapped to levels from Initial to Innovative, assigning numeric scores for team assessment.

Diagnosis is performed through four steps: silent reading, scoring, “playing cards” (or gestures) to justify scores, and consensus discussion, with the lowest individual score becoming the team’s item score and dimension scores calculated as averages.

Post‑diagnosis, improvement plans are created by selecting priority dimensions, defining higher‑level targets, analyzing gaps, and assigning owners and review dates, managed via Kanban boards (Fig. 8) that visualize tasks across teams and dimensions.

Agile measurement principles, inspired by Peter Drucker, emphasize external independence, holistic view, health, and balance. Metrics cover delivery value (rate, scale, completion), efficiency (cycle time, throughput), and quality (defect density, leak rate) (Fig. 10), with data used for team self‑comparison rather than cross‑team ranking.

The article concludes with practical success tips for agile maturity diagnosis and measurement, such as quarterly diagnosis cycles, time‑boxed activities, full‑team participation, concrete evidence for each item, and focusing on continuous improvement rather than scores.