Agile Transformation at JD.com: Practices, Metrics, and Lessons Learned

Opening

JD.com, the largest e‑commerce company in China, describes how it performed an agile transformation, the challenges encountered, the methods applied, and the outcomes achieved.

Background

JD Daojia, launched in 2014 as an internal project, became a strategic O2O service integrating logistics, fresh food, and supermarket products. In 2016 a team of over 20 engineers responsible for merchant onboarding was selected for agile transformation.

How to Transform

The transformation began with two prerequisites: gaining trust and reaching consensus with managers and directors, ensuring real support beyond verbal agreement.

Trust: managers must change their own management style and actions.

Consensus: align on quarterly goals, metrics, and demo schedules.

Performance Metrics

Metrics are divided into three performance‑management goals: improve individual performance, improve organizational results, and determine salary or promotion.

Increase personal performance through continuous learning.

Improve organizational outcomes by focusing on meaningful metrics rather than a long list of indicators.

Use performance data for compensation decisions, avoiding the bias of annual single‑point evaluations.

Metrics are further classified as internal (e.g., code lines, test coverage, defect count) and external (e.g., ROI, customer satisfaction, NPS). Selecting metrics should align with company goals, improvement focus, and data‑collection effort.

Two guiding principles: results matter more than process, and learning matters more than failure.

Push vs. Pull

After trust is earned, decide whether to push agile (mandatory adoption) or pull agile (voluntary, internally motivated). Pull is preferred for sustainable change.

Product Mapping

Using user story mapping to align the team around user‑centric product requirements. Steps include: each member writes story cards, arranges them in order, groups similar activities, and identifies the minimal viable set.

Key benefits: visual whole‑picture, shared understanding, and prioritization across importance and sequence.

Scrum

The team follows a strict Scrum framework with one‑week sprints, including planning, daily stand‑up, review, and retrospective meetings.

Planning: define what to do and how, produce sprint goal and backlog.

Daily stand‑up: 15‑minute sync answering three questions about progress, next steps, and impediments.

Review: product owner accepts or rejects completed user stories.

Retrospective: team inspects and adapts its process.

Experienced coaches are needed to handle unexpected issues during these ceremonies.

Pitfalls

Common traps include focusing on internal transparency without delivering customer value, leading to long merchant onboarding times despite improved communication.

Customer‑value indicators to watch: reduced onboarding time, faster response to merchant requests, merchant satisfaction, internal stakeholder response time, and internal stakeholder satisfaction.

Core of Agile Transformation

Gain trust and reach consensus.

Center on customer value.

Start with product demand mapping.

Adopt short iteration cycles.

Apply the Scrum framework.

Note

Scrum is not a magic solution; it merely exposes problems that the team must collectively solve.