How Doing KPT Retrospectives Changed Our Squad Culture: The Agile Growth Story of Oliveyoung's Order & Payment Squad

Oliveyoung's Order & Payment Squad introduced the KPT (Keep, Problem, Try) retrospective method to solve the problems of frequent human errors, superficial code reviews, and lack of communication.

For efficient retrospectives, they established four principles: sharing the retrospective topic in advance, senior-junior paired discussions, applying Time Boxing, and the principle of 'selecting one focus item for this quarter' to boost execution.

These efforts led to tangible results.

• Improved Code Quality: By introducing a systematic PR template that lets reviewers clearly grasp the intent and scope of impact of changes, they achieved early detection of over 90% of human errors before deployment.
• Established Collaboration Culture: By introducing a Slack-based daily scrum, they increased work visibility and reduced communication costs among team members.
• Improved Service Stability: To solve complex logic issues in the cart/order area, they introduced cart caching, reducing DB load.