Inbound Team Adopts Scrum to Improve Domain Understanding and Runs Sprints on a 2-Week Cycle

The Inbound Team adopted Scrum to overcome the limitations of the existing feature-distribution style of development and to enhance domain understanding across the entire team. This is part of the Agile methodology, which responds nimbly to frequent requirement changes and builds waste-free products by implementing only core features.

Scrum Team Structure and Roles

A Scrum team is small but complete, typically consisting of around 7 members. The main roles are as follows.

• Product Owner: Defines business requirements and manages the product backlog
• Scrum Master: Supports Scrum proceedings, estimates Story Points, and removes obstacles within the team
• Development Team: Developers, planners, designers, etc. who implement the product requirements

Sprint Operation Process

The basic unit, the Sprint, is set to a 2-week period, during which the priority of other issues is lowered to focus on achieving the Sprint goal.

• Story Point: Measures task difficulty based on the Fibonacci sequence, agreed upon based on relative difficulty rather than absolute effort.
• Daily Stand-up: Held for 15 minutes starting at 10:30 AM every day, where each member shares their issue report. If detailed discussion is needed, a separate meeting is held afterward.
• Deployment: Regular deployment is carried out once a week on Tuesdays to reduce communication costs. Urgent operational issues are handled on a separate schedule.

Retro and Improvement

After a Sprint ends, a 30-minute retrospective is held to improve the process for the next Sprint. Opinions are written anonymously, prioritized through empathy emoticons, and then discussed by dividing them into the categories Start (things to start), Stop (things to stop), and Continue (things to continue). Through this structure, team members are establishing an efficient way of collaborating regardless of their individual MBTI tendencies.