Agile Scrum Practices and Process Management in the ShareSave Project

Introduction

On November 11, Xiaomi launched the cross‑border e‑commerce platform ShareSave in Indonesia and partnered with the short‑video platform Likee to drive traffic and boost sales of Xiaomi ecosystem products overseas.

Agile Development Overview

Agile Development is a software development approach that embraces rapid requirement changes through iterative, people‑centric processes; Scrum is a standard framework for implementing Agile.

The ShareSave project has completed two iterations, and the team has mastered Scrum practices. This article shares their preliminary experience to help other teams adopt Scrum.

1. Sorting and Selection (爬梳剔抉)

1.1 Initial Product Backlog

The product backlog is a pool of requirements (a "demand pool"). The team used brainstorming with cards and voting to identify core processes of the ShareSave “group‑buy” flow (opening a group, sharing, downloading, payment, etc.). The core workflow includes:

Core Process Mapping: The Product Owner placed the 12 core processes on blue cards in a horizontal line.

Pros and Cons Description: Team members marked advantages with green cards and disadvantages with yellow cards.

Emotional Curve Chart: Processes with many green cards were moved up, yellow‑heavy processes down, forming a curve that reflects user sentiment.

Process Suggestions: Red cards captured improvement ideas for highlighted pain points.

Voting: Each member received five green‑dot votes; the red‑card idea with the most votes was selected as the best suggestion.

The Product Owner then compiled a product backlog that covers at least two iterations to ensure a sustainable development rhythm.

1.2 Refined Product Requirement List

The Product Owner filtered the backlog, collaborating with the Scrum Master to ensure the selected items can be delivered within a single iteration. Large items were split, and the scope was repeatedly refined until a final requirement list was produced.

2. Practicing Scrum

2.1 Task List

During the iteration planning meeting the team decides:

What to do (the selected requirements).

How to do it and who will do it (tasks entered into the task board with clear owners).

Scheduling to identify any resource bottlenecks and adjust priorities accordingly.

2.2 Task Board Rules

Task progress updates are maintained by the responsible team members.

Daily stand‑up meetings are used to synchronize the board and inform downstream colleagues.

Before handing over to QA, developers must perform a “smoke test” (one of the Definition of Done criteria).

2.3 Sprint Burndown Chart

The burndown chart visualizes task progress; a line below the ideal trajectory indicates the team is ahead, while a line above signals a risk of delay.

2.4 Daily Stand‑up

The 15‑minute stand‑up answers three questions: What did you do yesterday? What will you do today? Any blockers?

3. Moving Forward

3.1 Iteration Review

At the end of an iteration the team demos the completed features, with members acting as users to provide feedback and suggestions.

3.2 Iteration Retrospective

The team uses a “Sea‑Star Retrospective” divided into five quadrants:

Continue: Practices that add value and should be kept.

Stop: Activities that hinder progress and should be eliminated.

Do More: Actions that have proven beneficial and should be expanded.

Do Less: Efforts that consume resources without sufficient return.

Start: New ideas or experiments to try in the next iteration.

Team members place their thoughts on cards in the appropriate quadrant, vote with green dots, and highlight core suggestions with red dots. The Scrum Master then summarizes and discusses improvement actions.

4. Rules and Process Management

4.1 Iteration Calendar

The team follows a two‑week sprint cycle:

Week 1 Tuesday – Sprint planning: split requirements and confirm schedule.

Week 2 Tuesday – Product Owner evaluates next‑round requirements; UI designs and RD assesses solutions.

Week 2 Friday – Scrum Master finalizes the preliminary plan for the upcoming sprint to mitigate risks.

4.2 Process Management

Based on identified gaps, the team defined its own project process standards covering product planning, requirement review, scheduling, and change management, aligning with overseas e‑commerce best practices.

5. Summary

Through rapid iterations and embracing change, the ShareSave team has fully adopted Agile practices under the guidance of an Agile coach, continuously refining their workflow to deliver better product outcomes.