Agile Development Process and Team Practices for HR System Project
This report details how the HR system team adopted agile methods—including user‑experience mapping, Sprint 0 preparation, backlog planning, Kanban boards, daily stand‑ups, burn‑down analysis, demo sessions, and retrospectives—to improve delivery speed, quality, and business collaboration.
Project Background – The HR system team, formed in April 2019, aimed to provide operational tools for HRBP, COE, and SSC while establishing a standardized, process‑driven HR information system. Resource constraints and complex business scenarios initially caused delays and quality issues.
Adoption of Agile – Guided by mentor Du Weizhong, the team switched to agile development, increasing business involvement and process transparency, which boosted development efficiency and delivery quality.
User Experience Mapping – The first user‑experience mapping workshop was held to visualize business scenarios, clarify core project functions, and provide material for backlog creation.
Sprint 0 Preparation – The initial sprint included team composition, backlog definition, iteration planning, technology selection, architecture design, and UI/UE reviews.
Iteration Planning – The backlog was broken down into minimal development models and cycles (4‑week iterations with 2‑week sprints). Complexity was assessed using planning poker.
Complexity Analysis – Ensured high‑complexity features were split into smaller tasks for smoother flow and enabled velocity tracking for process control.
Development Phase – Consisted of three core practices: Kanban board, daily stand‑up meetings, and velocity/burn‑down tracking.
Kanban – Comprised task list, metrics area, and impediment area; team members moved cards to reflect progress and recorded complexity and actual completion time.
Daily Stand‑up – Held at 18:00 for 10 minutes, covering completed work, next day’s tasks, and any blockers.
Burn‑down Chart – Used to assess project health; significant deviations prompted event logging for later retrospective analysis.
Demo Meetings – Conducted every two weeks with business stakeholders to showcase features, gather feedback, and adjust the backlog for the next sprint.
Retrospective Meetings – Facilitated by the mentor to boost morale and improve processes, using a learning matrix (good, bad, ideas, thanks) to capture insights and identify improvement actions.
Summary – The mentor system’s first iteration is live, with accelerated development speed and enhanced alignment between delivered products and business needs. The agile framework has strengthened team cohesion and commitment to serving the group’s HR operations.
DevOps
Share premium content and events on trends, applications, and practices in development efficiency, AI and related technologies. The IDCF International DevOps Coach Federation trains end‑to‑end development‑efficiency talent, linking high‑performance organizations and individuals to achieve excellence.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.