My Journey with Agile Development and Extreme Programming: Lessons and Impact

In 2008, a chance encounter sparked a strong interest in Agile development, leading me to spend a weekend reading Kent Beck's book Extreme Programming Explained , over 200 pages of English text, which profoundly shocked me with its ideas and practices.

Having worked in software development for eight years, I had never imagined development could be approached this way; after a demoralising project, Agile acted as a powerful antidote, restoring my confidence in software project management. By applying XP, I discovered that many contradictions in the waterfall model—such as waiting for fully clarified requirements versus a fixed deadline—could be resolved by breaking requirements into independent user stories prioritized by business value, allowing immediate development of high‑value, clear stories while clarifying others. Another dilemma, whether to test before or after code review, was solved through test‑driven development (including automated testing) and pair programming.

In a subsequent new project we practiced Extreme Programming and completed the work a quarter ahead of schedule, earning high praise from the client.

1. Continuous communication and complete transparency of the delivery process let the client clearly perceive progress. 2. All of the client’s requirement changes were met promptly.

Many Agile principles completely overturned long‑standing waterfall mindsets, representing a transformative upgrade in my thinking.

Of course, Agile is not a silver bullet; years of practice have shown that Agile transformation is difficult, and even with Agile each project remains challenging. Nevertheless, it opened a new window, adding powerful tools to our arsenal. This is why my early Agile training was titled “Is there another way to develop software?” —not to hard‑sell Agile, but to show that software development is not limited to a single waterfall path. If your toolbox contains only the waterfall model, you are confined to solving problems within that framework, severely limiting your ability to address issues. Waterfall seeks certainty, yet software development is full of uncertainty, especially for Internet products where users and requirements are volatile; Agile emerged to adapt to this uncertainty, with adaptability as its core. Lean thinking and Kanban further enrich this toolbox.

In the past decade, Agile and Lean have evolved from mere development and production‑management methods into a mindset and even a new way of corporate survival, suited to the VUCA era (Volatility, Uncertainty, Complexity, Ambiguity). Values such as rapid feedback, decentralisation, collaboration, collective decision‑making, information sharing, flexibility, transparency, and visualisation are becoming consensus. Organisations are shifting from hierarchical to flat structures, with decision‑making moving from top‑down cascades to autonomous small groups operating under a corporate framework—essentially internal entrepreneurship. The clothing brand Han Du Yi She exemplifies this transition: starting as a simple Taobao brand, it grew from ¥200 k to ¥1.5 billion, moving from a pyramid‑controlled model to a product‑team model where each 1‑to‑3‑person team (designer, sales guide, tailor) decides on style, price, quantity, discounts, promotions, and internal allocation, while the company provides shared resources and evaluates core metrics, fostering internal competition and rapid decision‑making.

In product design, the approach has shifted from striving for perfect plans at the outset to starting with a Minimal Viable Product ( MVP ), delivering it quickly for user feedback, and iteratively improving it in a spiral manner. For example, when Tencent launched WeChat in 2011, the initial version was extremely simple, yet because it delivered the core messaging function, it quickly gained market acceptance and, after years of evolution, became a leading mobile platform. At launch, no one could predict market acceptance, target audience, or competition; the MVP stage served to validate the idea, and if feedback was poor, the product could be adjusted or abandoned. Speed and rapid trial‑and‑error have become the survival rule for enterprises and products today.

Undoubtedly, Agile thinking has profoundly changed me, influencing not only software development but also my perspectives on project management, team leadership, and personal conduct. Although I may not have mastered it fully, I believe without this cognitive upgrade I could not have improved further. How has Agile impacted you?