Share Visibility of Feature Flag Usage Across Teams
Without proper visibility of feature flag usage and status across teams, flags can do more harm that good. Using robust dashboards and alerts to understand who owns a flag, why it was created, how long it has existed, and what percentage of users are seeing the flagged feature vs. not is useful to organize the potential flag chaos. Further, this visibility goes across teams, and allows dev and ops to work off of shared flag information to get a release out the door, creating better collaboration and speed of release.
A System for Logging Changes
In order to track changes better, consider logging all the changes to a feature flag so you can track who introduced a change and at what time. In distributed teams, this can save numerous hours in figuring out who is responsible or has the rights for a particular change. The effects of feature distribution are not restricted to the engineering team- you should log the feature status to your usage analytics, support systems and more. With CloudBees Feature Flags, we have exposed the impression handler to facilitate reporting to all your different platforms.