flâneur

A/B & Gradual Rollout — The Same, But Different | by Nir Boger | Medium

nir-boger.medium.com · 842 words · saved by 1 readers

People ask me: “Nir, what is the difference between A/B testing and Gradual rollout?” This post will try to give an answer to this question When we refer to Gradual Rollout we are talking about a methodology of deploying a new feature to the users by degrees, rather than deploy it suddenly to all of the users There is 1 reason for gradually rolling out new feature and the reason is to: reduce the risk when deploying a brand new feature So you have the most talented QA team. The QA team found all the bugs on your feature, but does the QA knows if it works for the user? Let’s explain it using an example: Now you have 2 options: Let’s imagine that your users start complaining to your support that after 3 days the device turned off with no reason consistently. Your engineering team investigate this issue and find out it happens only to users that have linked their exchange account to their device, and it is happening only after only 3 days… The engineering team then fix this bug and a new

Press enter or click to view image in full size Ab Culture Ab Testing A/B & Gradual Rollout — The Same, But Different Nir Boger 4 min read · Feb 3, 2014 -- Listen Share People ask me: “Nir, what is the difference between A/B testing and Gradual rollout?” This post will try to give an answer to this question Gradual Rollout When we refer to Gradual Rollout we are talking about a methodology of deploying a new feature to the users by degrees, rather than deploy it suddenly to all of the users Why? There is 1 reason for gradually rolling out new feature and the reason is to: reduce the risk when

related reading