Journey to #SLSPWAYOFWORK (0/?)

Once upon a time, there was a?bank, a standard bank with standard daily business routines and habits. Internal IT was perceived as a cost center, business was focused on generating tons and often changing ideas hand in hand with blaming game about missed deadlines, increased efforts, and rising costs. Both Business and IT were focused on 3 weekends of the year when their activities were deployed into production as new changes. Delay was expected for every single release because the next release date was too far for some changes to be postponed. Releases were cosmic/massive, error-prone, with huge requirements, that were often changed during the implementation process. Days after release were also huge pain, as bugs in deployed changes were causing issues/incidents in the operations of the bank.

Does it sound familiar to you? (No, it is not the Phoenix project ?? )

It surely does to me. It was the reality we were living in a few years ago. But we decided to change it.

What did we change? The simple answer is EVERYTHING. From versioning tool, to how the investment plan of the whole bank is prepared and executed. And of course, this is not a story about IT changing bank, it is a story about changes we did in the bank over the time

Disclaimer: This is not a story to follow, this is a story to read and similarly have fun as we had ??

First step: make IT a reliable partner (To be continued)