The term hot-fix can sometimes be used incorrectly by teams that want to release a feature or small fix out of the regular release cycle. When out of cycle releases happen, it risks issues being introduced due to changes not being properly tested or impact in areas that are not anticipated, which is why any out of cycle release should be done with extreme caution.
With every project team having their own feature priorities and deadlines, the challenge is making an unbiased decision for whether an out of cycle release should happen based on data, not goal completion, with little to no user impact.
In the talk I’ll discuss how teams can take back the term “hot-fix” by measuring quantitative vs. qualitative data, moving away from a release cadences based on feature readiness to a set release cycles. This discussion will include how to navigate those teams trying to release their features to meet their own goals and deadlines, the process of finding a solution to consistent out of cycle releases, as well as the process of creating a scalable unbiased solution.
Comments