How Agile Testing Transforms Global Projects: Lessons from the P1 Initiative

In the previous episode we discussed global solutions for maps and messaging; this episode focuses on applying agile testing in global projects.

Agile Testing Definition

When we mention Agile Testing (Scrum Testing), we need to understand what it is and how it differs from traditional testing.

First, see a diagram comparing traditional and agile testing:

The diagram shows that traditional testing aligns with the waterfall model (requirement → design → coding → testing → release). Agile testing emphasizes interaction and increment; each story can be designed, coded, and tested, promoting rapid design, coding, testing, and release while maintaining interaction among product, development, and market.

Agile Testing in the P1 Project

1. Deliver working software frequently with short delivery cycles

P1 is a key project for Q1; version 1.0 must be launched on 2020‑03‑01. Because of the short timeline, the principle was to ensure core business flows work without affecting usage, i.e., Scrum Testing’s core principle: deliver working software.

2. Face‑to‑face communication is the best way to convey information

During testing, three Scrum meetings were held. The daily stand‑up gathered blocked issues; the test lead summarized and fed them to developers, with severe issues resolved within three hours. A daily bug‑triage meeting classified ~400 bugs into three categories: (1) core‑business impact – must fix; (2) UI issues – critical ones fixed, others deferred; (3) translation issues – postponed.

The third Scrum meeting, initiated by project management, reviewed overall test status to spot risks early.

3. All team members must cooperate every day

The team used a “small black room” co‑working mode, enabling face‑to‑face problem solving, rapid developer debugging, and quick test verification, greatly improving communication efficiency and saving delivery time.

4. Pursue technical excellence and good design

Testers continuously improve techniques, participate early in requirement and design reviews, and drive better architecture and user‑centric product design, effectively practicing Test‑Driven Development (TDD).

5. Simplify the test process

Traditional testing follows test‑env → gray‑env → pre‑release → production. For V1.0 targeting overseas markets with no live users, the team decided to validate and accept in the production environment, saving time for both testing and release.

Conclusion

Agile testing aligns with the Agile Manifesto, follows agile development principles, and integrates with the overall development flow. Practices include TDD, ATDD, pair programming, continuous testing, etc.

Key differences between traditional and agile testing:

Traditional testing separates developer and tester roles; agile testing can involve the whole team.

Traditional testing is phase‑based; agile testing emphasizes continuous testing and feedback.

Traditional testing distinguishes verification and validation; agile testing treats them as a unified, user‑need‑centered activity.

Traditional testing records every defect for root‑cause analysis; agile testing stresses face‑to‑face communication, collaboration, and shared responsibility.