Moving quickly in today's age is critical to a financial institution's success as technologies and practices continue to rapidly evolve. To keep up with the ever-changing needs of customers, banks and credit unions must stay agile.
Part of staying agile and improving means constantly updating products to keep them at optimal performance. But updates can cause lags, downtime, and frustration for both institutions and their customers. Knowing this, Narmi has adopted a process for rolling out updates that’s smooth, fast, and stress-free for institutions and their digital banking end-users.
Narmi’s new release cycle for updates prioritizes stability while also prioritizing continual improvement – something achievable thanks to the principles of continuous delivery and continuous deployment. This practice ensures Narmi’s innovations stay reliable, with minimal impact on dependable access and user experience. This results in fewer outages, fewer bugs, and greater control for our customers.
With the new release cycle, Narmi’s software products will see a reliable, dependable, and regular cadence of updates every six weeks. The high frequency of updates means smaller batches of fixes that won’t overwhelm our products, end-users, and customers. And a regular schedule means institutions get advanced notice of feature changes that may impact them and their end-users, giving them time to test, validate, and respond with feedback.
If for any reason a new feature is not needed, institutions can opt-out of individual releases. Finally, continuous deployment means that bugs are fixed as they’re found, resulting in fewer interruptions for users.
On the first Monday of each month, updates, fixes, and anything else to be released is deployed to a testing or “canary” environment. There, it undergoes a round of tests where any potential bugs are detected, prioritized, and mitigated. As the bugs are squashed, these fixes are automatically deployed.
Once this early version passes all its tests, a stable version is created and automatically deployed to further user acceptance testing (UAT) environments to be validated and approved. Every Narmi customer receives a dedicated UAT environment assuming they have a test core banking system. Finally, non-engineering implementation and/or development teams move to production and monitor the roll-out. In non-technical terms, every release is rigorously tested to make sure the new code and functionality is performing optimally.