How Taobao Live Boosted Efficiency with Agile Practices: A Real‑World Case Study

21CTO summary: At the first Alibaba R&D Efficiency Carnival, agile coach Wen Ju shared Taobao Live’s agile practice, showing notable gains in efficiency, quality, responsiveness, and on‑time delivery after three months.

When I joined the team at the end of May 2016, Taobao Live was a new business still exploring its product. The iteration was halfway done, requirements were not fixed, and development time was tight, requiring overtime.

Taobao Live is not a standalone app; it is released together with the main Taobao app in a “train” release model that enforces strict quality checkpoints and fixed release times. Missing a slot forces an emergency release, which brings many online issues and turns operators into customer‑service staff.

Metrics Used to Measure Agility

The team dashboard evaluates agility across four dimensions:

Capacity : amount of valuable feature points delivered per unit time.

Lead time : time from user request to delivery, the core agile indicator of responsiveness.

Quality : product survivability.

Predictability : ability to keep commitments.

Over the next three months we tracked these indicators.

Radar Chart of Progress

The radar chart shows improvements in the four dimensions plus a crucial business‑metric dimension. Specific business numbers are omitted for data‑security reasons.

Process Indicators

Completed Requirements

The dip in July was due to two urgent requirements that disrupted the rhythm; August showed a rise when no interruptions occurred.

Lead Time

July’s lead time spiked because of the urgent tasks, highlighting the need to protect the team’s cadence.

Requirement analysis time decreased from June to August thanks to product and UED efforts, while testing time grew modestly due to balanced workload distribution.

New Defects

From May to August, total defects and severe defects continuously declined, indicating higher test quality.

On‑time Delivery Rate

June and August achieved 100% on‑time delivery; July slipped due to the urgent requirements.

Behind the Changes – Focusing on Business Goals

We created a physical business‑goal board updated after each product release. The board visualized key metrics, fostering team discussion and alignment.

After defining business goals, we identified a main line to achieve them, ensuring “first‑things‑first”. The main lines for July‑September were host quality & conversion, channel & interaction upgrades, and interactive marketing.

Product proposals must be tied to measurable business impact, such as increasing daily live sessions or host activity.

Behind the Changes – Rapid Hypothesis Validation

Innovation requires fast fail‑fast cycles. We piloted two homepage features—10‑second video playback and animated “like” effects—by releasing prototypes to 1‑5% of users, gathering data within 24 hours, and iterating in just two days.

Behind the Changes – Collaborative Requirement Refinement

Initially, requirement analysis was slow and fragmented. We formed small cross‑functional requirement groups (≤5 members) comprising product, design, development, and testing, enabling simultaneous refinement and reducing hand‑off delays.

Behind the Changes – From Mini‑Waterfall to Continuous Delivery

Switching from a mini‑waterfall to continuous delivery spread testing and defect fixing across the iteration, reducing end‑stage pressure.

By August, defect inflow was distributed over ten days instead of the last three, easing tester workload.

Behind the Changes – Continuous Improvement

When a team voluntarily and continuously improves, it matures into a high‑performing unit. The team’s iteration retrospectives identified actions such as improving review efficiency, which remained in practice through 2017.

Follow‑up visits in January 2017 confirmed that the board, requirement groups, and other agile practices continued to boost efficiency and product quality.