How a Jakarta Bank reduced deployment time by 66% by streamlining software delivery with modern practices

A leading commercial bank in Jakarta partnered with Greyamp Consulting to embark on a transformative journey to overhaul their traditional software development methods. Greyamp facilitated the bank's aim to enhance efficiency, foster innovation, and streamline the software development lifecycle. Existing processes, plagued by inefficient source code management and lengthy cycle times, hindered delivery teams and impeding overall progress.
Read More
Challenges

These are  the challenges that we were facing

Prolonged merge times
Developers' reliance on local copies of the source code and long-lived branches lead to large, complex merges. This causes merge delays and increases the probability of merge conflicts.
Schema Conflicts and Collisions
Direct changes to the schema during development caused conflicts and collisions, introducing complexities and hindering smooth database evolution.
Integration Testing Issues
Delayed merging of changes and a lack of an continuous delivery approach resulted in trivial bugs emerging during later-stage integration testing, disrupting the stability of the staging environment.
Audit Trail Deficiency and Schema Rigidity
Developers lacked a focus on data availability for troubleshooting future production errors. The absence of audit trails, data loss over time, and inflexible schema limited adaptability and responsiveness to evolving business needs.
Solutions

To address these challenges, we recommended and enabled the bank to implement a series of solutions

Enhanced Development Workflow
Trunk-based development was adopted, designating a single "trunk" branch as the source of truth and streamlining the development process.
Continuous Delivery Optimization
Bug-fix branches were created to address issues, ensuring a seamless continuous delivery cycle for reliable and efficient software deployment.
Continuous Delivery Optimization
Bug-fix branches were created to address issues, ensuring a seamless continuous delivery cycle for reliable and efficient software deployment.
Comprehensive Change Tracking
The team was encouraged to maintain detailed and systematic change-logs for all schema changes, ensuring transparency and auditability.
Outcomes

The implemented solutions yielded significant improvements

Single Source of Truth: Trunk-based development reduced maintenance overhead and improved collaboration within the 12-member team. Merging time was reduced by 70-80%, and the number of bugs encountered in integration tests decreased by 30% sprint-on-sprint.
New tools and practices: Recommendations were made for tools and practices supporting improved audit trails, database schema evolution, and enhanced code quality through unit testing frameworks integrated into the continuous delivery pipeline.
Continuous Delivery Practices: Adoption of continuous delivery practices reduced deployment cycle time from 9 months to 3 months.
More Case Studies

Checkout Some Of The Articles From Our Blog

Rapid Experimentation with Digital Teams for Lean Pivoting, at a Bank in Jakarta

A business unit within a large Bank, that had a need for rapid experimentation...
Read More

Enabling a team of DevOps Engineers to manage the entire Digital Banking Platform

A large bank in Indonesia wanted to build a complete Digital Banking.....
Read More

Taking learning to the eXtreme - 24 Week Talent Attraction Program for a Pension Bank in Indonesia

A Pension bank in Indonesia wanted to....
Read More
Case Study
Launching a Digital Bank in Record Time in Taiwan - Rolled out MVP in 8 months
Project Overview
One of the prominent banks in Taiwan wanted to build a digital bank that would disrupt the market. This was a huge ask as we needed to change the way of working within the bank to a rapid iterative one. The bank wanted to become more outcome-driven which was fueled by early feedback and customer-centric product development design.
Challenges
Aligning the entire team to a common purpose
Tight timelines and high delivery pressure
High Reputation risk if the launch did not go right
Getting the initial buy-in from leadership, as they were new to agile
Establishing effective communication channels within the org and vendor partners
Outcomes
1
MVP of product rolled out within 8 months
2
Successfully captured the market and continues to be one of the top apps in the Taiwan market
3
Enabled effective communications for early feedback to establish business value
4
Built a working relationship with the vendor partner based on agile tenets of working
Solutions Provided
1
Worked with the team to bring them up to establish the “Way of Working” based on Agile principles
2
Integrated the delivery process with the vendor partners, working as a Single Team, till ”Go-Live”
3
Adaptive Planning to maximize business value while working with constraints
Back