How we accelerated developer velocity by going back to basicsCheck Reference
Close to 6 months back, our team was given a target to increase the developer velocity among other things. Developer velocity was being calculated in terms of “number of release per engineer per week”. With a 5 engineer team, it meant that we make a release every single day. At that time, we were in once a week release mode. Mind it, there aren’t any QAs in the team as well. So in this talk, I am going to reveal the secrets of how we went ahead and changed our way of working to achieve this seemingly unachievable goal. It was all made up from doing things like doing away with feature branches, extensively using feature flags, experiments, kill switches, changes in code review process, increased focus on unit test coverage, leveraging automation tests written in cypress and so on.