Skip to main content
    DevOps
    Way of Working
    1. Home
    2. Capabilities
    3. Release Feature Flags

    Feature Flag Governance

    Acceleration
    Phase: release
    DF
    LT

    Quick Reference

    Phase
    release
    Epic
    Advanced Release Coordination
    Milestone
    Acceleration
    Target
    >= 80% features use flags
    Implementation Time
    Part of Advanced Release Coordination epic: 3.5 weeks (23 hours per capability avg)

    What & Why

    Definition

    >= 80% of new features deployed behind feature flags with automated cleanup of flags older than 90 days.

    Business Value

    Reduces rollback time from 2 hours to 5 minutes and enables progressive rollouts reaching 50% of users in 2 hours vs 2 days through feature flags Achieving >= 80% features use flags is a key milestone toward this goal.

    Context

    This capability is part of the Acceleration milestone's focus on scale automation, embed compliance, improve speed & reliability. Essential for teams targeting DF, LT improvements.

    Success Criteria

    Target

    >= 80% features use flags

    Measurement

    Feature flag usage rate + flag age tracking

    Evidence

    • Feature flag config
    • Flag usage metrics
    • Flag cleanup logs

    In Practice

    Real-World Implementation

    Teams use LaunchDarkly/Unleash for feature flags, deploy code with flags off, gradually enable for user segments, remove flags after full rollout.

    Concrete Example

    Feature 'New Checkout' deployed behind flag 'checkout-v2'. Enabled for internal team (dogfooding) -> 10% users -> 100%. Flag removed after 30 days.

    Implementation Guide

    Prerequisites

    Continuous Deployment to Non-Prod
    >= 90% merges auto-deploy within 15min

    Implementation Steps

    Follow the measurement approach: Feature flag usage rate + flag age tracking

    For detailed step-by-step guidance, refer to the Advanced Release Coordination Implementation Kit.

    Resources

    Implementation Kit

    Advanced Release Coordination Kit

    Templates

    Browse all templates

    Related Resources

    View learning paths

    Related Capabilities

    Prerequisites

    Implement these first

    Continuous Deployment to Non-Prod

    Complementary

    Often adopted together, from the Advanced Release Coordination epic

    Release Cadence Coordination
    Release Health Dashboard
    Release Dependency Graph
    Release Rollback Testing
    Release Metrics Analytics

    Troubleshooting & FAQs

    Common Issues

    Issue: Target metric not improving

    Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness

    Issue: Team resistance to adoption

    Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition

    Issue: Inconsistent implementation across teams

    Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards

    Frequently Asked Questions

    Can we implement this before completing prerequisites?

    While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.

    How long does implementation typically take?

    Most capabilities can be implemented within 90 days when tackled as part of the Acceleration milestone. Individual timelines vary based on team size and existing practices.

    DevOps
    Way of Working

    DevOps practices for the entire delivery lifecycle

    © 2019-2026 devopswow.com. Created by Burhan Öcüt

    PartnersAboutPrivacyTermsCookies