You Can’t Scale Feature Flag Usage Without Visibility and Governance Across the Software Delivery Lifecycle

The Wild West: great inspiration for movies and fashion, not so much for development teams It Starts With Feature Flag Management Visibility and Control One of the main reasons companies move from no flag management system or a limited “homegrown” feature flag management system is the lack of visibility into flag status and owner. An […]

The Wild West: great inspiration for movies and fashion, not so much for development teams It Starts With Feature Flag Management Visibility and Control One of the main reasons companies move from no flag management system or a limited “homegrown” feature flag management system is the lack of visibility into flag status and owner. An environment-based permission model is essential for helping bring more personnel into the process of feature management across development, product, marketing and even sales, but the next step past basic authorization is change approval requests. They’ll ask, “If we use feature flags at scale, how will this impact our technical debt over time?” Or, “How do we migrate our old flags into a new system—and what is the time and technology investment required to get a team scaled on using the tool?” Shortly thereafter, we will typically get questions around visibility and governance: “How can we control who is allowed to update a flag?
Source: CloudBees