From Branch Merge Hell to Trunk-based Development – A Bank Agile Case Study 2/n
ShriKant Vashishtha
Agile Consultant | Author of “Agile Estimation Distilled” | Ex-Director at GlobalLogic, Xebia | Open-Source Contributor
Lots of organizations are desperately trying to bring agility in their enterprise IT. In many such cases, enterprise IT stands on the worn pillars of traditional Waterfall process and legacy products.
The business in such orgs sees IT as a black hole where no business need can escape from inside it. The reason being, traditional process and legacy systems take months of cycle time to deliver almost any business need.
This results in a frustrated and desperate stakeholders who threaten to try anything or everything under the sun to get tangible outcomes.
This case-study is a story of a bank which was almost at the verge of outsourcing its entire IT. The bank since has moved on to become one of pioneers in banking innovation space. The bank focuses to serve its customers with innovation and agility in its offerings.
In the first part of the case-study, we looked at the difficult conditions the team lived in. That was more to do with technical processes they used for handling multiple projects at the same time. This part focuses on how they moved on from the branch merge hell they lived in.
Solution Architect | TOGAF | Shoppers Experience |Java | Microservices |Graph QL | SpringBoot | Gen-AI | Vertex AI | AZURE | Reactive | Kafka | Swagger| Micrometer Logging | Prometheus | Mainframe Modernization
6 年I agree it is easy to maintain if there is single code branch. What branching strategy agile recommends if delivery timelines of feather releases are different. Keeping everything thing in one branch will introduce the risk of half cooked code of other feature deliver in production.
Tech Lead at Roosterlandia with expertise in Agile Coaching
6 年Bo Henning J?rgensen