Agile Transformation of the Agricultural Bank’s “Spring” Project: One‑Year Retrospective and Live Q&A

Software development is inherently uncertain, and agile methods embrace this by treating development as a design process rather than a manufacturing line, allowing teams to adapt through iterative control and frequent feedback.

The “Spring” project, launched in July 2017 by the Agricultural Bank’s R&D Center Application Development Department, built a mobile marketing platform to support the bank’s “Spring Action” initiative. From the start, the project faced heavy workloads and vague requirements, making it a challenging candidate for an agile pilot.

After more than a year of agile practice, the team reported improvements in culture and engineering efficiency, prompting other bank departments to explore agile practices and share resources. The success led to a DevOps+LIVE technical livestream featuring the project office’s agile support team and ScrumMasters.

The livestream addressed ten audience questions, covering topics such as how the bank reconciles rapid iteration with strict quality controls, the mapping of requirements to user stories and releases, status granularity evolution, gaining leadership and business buy‑in, the perceived cost of story‑point estimation, metrics for measuring agile impact (e.g., lead time), coordination with non‑agile teams, organizational adjustments, integration of TFS electronic boards with physical kanban, and the extent of Microsoft technology usage within the bank.

ScrumMaster reflections emphasized three key lessons: the importance of regular retrospectives for continuous improvement, the need for unified team thinking and clear role definitions, and the necessity of sustained commitment to agile principles rather than treating them as a short‑term experiment.

For the full video and additional DevOps articles, readers are directed to the original links provided at the end of the article.