Spring Project Agile Transformation: Integrating Physical Kanban with TFS for Process, Version, and Delivery Improvements

The "Spring Project" team was the first in Application Development Department II to adopt an agile model, using Scrum with a "board + stand‑up" approach and gradually integrating TFS tools with a physical Kanban board.

Physical Kanban served as the core daily management tool, enabling two‑week iterations, user‑story mapping, and visible progress tracking, but presented challenges such as unclear story hierarchy, difficult archival retrieval, manual data collection, and ambiguous code‑story mapping.

To address these issues, the team implemented seven measures: (1) managing requirements and user stories with TFS work items; (2) linking code to work items; (3) splitting the Git repository into 17 module‑specific repos; (4) establishing TFS branch policies for simple code reviews; (5) creating BUG branches with pull requests for fixes; (6) isolating builds and automating deployment via continuous integration; (7) using dashboard widgets to monitor daily builds and deployments.

These actions enabled clear requirement‑story linkage, automated data collection, transparent code reviews, isolated module development, and reliable automated build‑deploy pipelines, significantly improving version management and delivery frequency.

Overall, the seven measures allowed electronic tracking of requirements and stories, combined with physical Kanban for clear progress control, and leveraged TFS features to enhance continuous integration and delivery capabilities, leading to steady efficiency gains across the agile pilot projects.