Agile Process Improvement: Case Studies and Practical Insights

Author Introduction Li Juan, Process Improvement Director at Qunar, with 15 years of software project management experience at Yahoo China, Alibaba, Tencent, and Qunar, specializes in problem analysis and process improvement.

Agile has become popular, but it is more than stand‑ups, continuous integration, or test‑driven development; it represents a cultural shift from mindset to practice. Teams must first clarify why they adopt agile, the problems they aim to solve, and the value they expect.

Case 1: Responding Flexibly to Change A product director complained about project delays; the author highlighted that teams cannot expect stable requirements and must improve their ability to adapt. Visibility through story/task breakdowns and Kanban boards, daily stand‑ups, and clear assignment enable rapid response.

Case 2: Efficient Communication and Collaboration In a mobile app team (iOS, Android, backend), traditional stand‑ups were ignored because members saw little relevance. Re‑organizing into cross‑functional delivery teams aligned by product line increased communication, as members now shared common goals.

Case 3: Goal‑Aligned Teams A declining process was traced to weak virtual team structures and narrow responsibility scopes. Strengthening team ownership and expanding scope across systems restored cohesion and delivery capability.

Case 4: Robust Engineering System and Culture Scaling Scrum requires resources and quality discipline. The author discusses the cost of resources, the need for multi‑skill engineers, and the importance of maintaining quality through unit tests, continuous integration, and code review. Google’s monorepo model is cited as an example of a strong engineering culture.

Overall, the article emphasizes that a truly agile team—rather than just agile practices—requires clear visibility, low‑level decision‑making, decoupled yet cohesive responsibilities, sustained team size, and a culture of ownership and quality.