This Is How Our Development Culture Grows

This post summarizes how the FINDA Cash Growth PG Asset/Credit Management PT built and changed its development culture. The core isn't simply adding rules, but creating a structure where team members share, trust each other, participate openly, and grow by stimulating one another.

Initially, sprint operations were loose. The Daily Scrum ran long, breaking focus, and low utilization of Jira/Confluence meant progress wasn't visible at a glance. Retrospectives and backlog organization were also insufficient, creating a high risk that the same problems would recur.

Afterward, the process was significantly overhauled.

• Fixed the Daily Scrum at 15 minutes, keeping sharing quick and issue-focused only
• Recorded Story Point, Start/End Date, and Work Log in Jira to manage progress transparently
• Made Code Review mandatory, changing the rule so that merging requires at least 1 approver
• Split retrospective and Backlog records by PT and by development group, reflecting them in the next sprint

Thanks to these changes, sprint status sharing became faster, code quality improved, and the likelihood of recurrence for issues raised in KPT decreased. Using more tools may feel cumbersome at first, but once it becomes habitual, it actually becomes a foundation that boosts the team's focus and growth speed.