Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Feature Flag Maintenance

Avatar for talianassi talianassi
October 12, 2020

Feature Flag Maintenance

Using feature flags in your feature releases is becoming the norm. Feature flags allow you to test your code in production, perform canary releases, and even conduct A/B testing. However, when you have a ton of feature flags, it can be overwhelming. How do you handle it? In this talk we will go through the entire feature flag lifecycle. This includes creation, naming conventions, workflows, reporting, and testing. You will walk away with a better understanding of how to manage your feature flags to be more productive.

Avatar for talianassi

talianassi

October 12, 2020
Tweet

More Decks by talianassi

Other Decks in Technology

Transcript

  1. FEATURE FLAG USE CASES TESTING IN PROD A/B TESTING KILL

    SWITCH SUBSCRIPTION MANAGEMENT MIGRATION TO MICROSERVICES
  2. INCLUDE TICKET NUMBER INCLUDE THE NAME OF THE SERVICE INCLUDE

    THE NAME OF THE TEAM THAT THE FLAG BELONGS TO INCLUDE THE NAME OF THE FUNCTIONALITY CREATION
  3. IMPLEMENTATION DON’T CHANGE THE SCOPE OF YOUR COMPONENTS JUST TO

    SUPPORT FEATURE FLAGGING DECISIONS MAKE YOUR FLAGGING DECISION AS CLOSE TO THE LOGIC AS YOU CAN
  4. IMPLEMENTATION - TESTING Choose the most important flows to automate

    and test Work with your product owner to prioritize what these flows are Target your automation bots inside the feature flags
  5. ROLLOUT USERS SHOULD CONSISTENTLY HAVE THE SAME EXPERIENCE INCREASING EXPOSURE

    TO A FEATURE SHOULD NOT AFFECT THE CURRENT EXPOSED POPULATION
  6. ROLLOUT SET UP ALERTS TO PAGE YOU WHEN YOU GET

    ANY STATISTICALLY SIGNIFICANT CHANGES
  7. CLEANUP ASSIGN AN EXPIRATION DATE FOR EACH FLAG SET UP

    ALERTS THAT WILL POKE YOU WHEN A FLAG IS STALE
  8. CLEANUP ADD A SUBTASK TO YOUR BACKLOG TO RETIRE THE

    FLAG AT THE SAME TIME THE FLAG IS CREATED MAKE SURE YOU MET YOUR DEFINITION OF DONE