Banksalad EM Looks Back on the MyData Project: Lessons in Priority Setting and Technical Debt Management
Key point
A Banksalad EM shared experiences and reflections on priority setting, technology adoption, and collaboration methods encountered during the MyData project.
Details
Ha Jo-eun, Engineering Manager (EM) of Banksalad's Authentication Squad, shared the development process and retrospective of the MyData project, which began in April 2021. The project aimed to transition the scraping-based data connection environment to an API-based one, and to develop its own certificate, the 'Banksalad Certificate,' along with data connection features.
Priorities and Implementation Strategy
To address the lack of development time during the planning stage, priorities were reset into P0, P1, P2 tiers. Using 'whether it delivers core value to users' as the criterion, the team decided to focus on P0 and P1 features while implementing the remaining features incrementally. When adopting technology, Next.js and WNI (WebViewNativeInterface) were applied, and a POC (Proof Of Concept) was conducted to verify whether requirements were met and to identify potential issues in advance.
Collaboration Process and Retrospective
To improve collaboration efficiency, a 1 Pager document containing a summary, goals, non-goals, and plans was created, and a ticket-based workflow was built using Jira. Meetings were limited to under 30 minutes, with owners and deadlines clearly assigned. In the retrospective, it was emphasized that when adopting new technology, care must be taken not to waste time on 'non-goals,' and that overtime should be regarded as a last resort. It was also noted that company performance and individual performance should be kept separate to avoid over-attributing meaning, and that, for the sake of long-term productivity, the plan is to leave work early to deepen learning in functional programming and the Authentication field.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.