Feature flags allow developers to gradually rollout new features to specific users or groups, expand or rollback changes without redeploying code, and test features with real users. They separate code deployment from releasing business logic, enabling developers to get feedback and analytics before full release. Feature flags also eliminate long running branches and merge conflicts that occur in traditional release processes. The document recommends best practices for feature flagging like defining the right level of flagging, avoiding ambiguous or misunderstood flags, controlling access, adding visibility for non-technical users, and logging dependencies.

1. Feature flags to speed up
& de risk development
Edith Harbaugh, CEO & cofounder, LaunchDarkly
@LaunchDarkly LaunchDarkly.com

2. About Me
• Cofounder & CEO, LaunchDarkly
• Podcast cohost, “To Be Continuous”
• BS Engineering Harvey Mudd College
• Engineering, Epicentric & Vignette
• Product, Monster.com, EasyBloom, TripIt
• Marketing, Concur

3. Tsunami Software Releases
@Edith_H

4. Feature Flags
@Edith_H

5. Feature Flags!
• Push functionality to who you want, when
you want
• Expand or roll back, without a new
deployment
• Separate code deployment from business
logic
• Get real-world feedback and analytics
• No more long running branches with merge
conflicts

6. Use Feature Flags to expose
functionality when you want, to
who you want
@Edith_H

7. Early Access Betas

8. Opt-In
@Edith_H

9. Block
@Edith_H

10. Rollouts
@Edith_H

11. Run A/B Tests
@Edith_H

12. Newbie > Power User
@Edith_H

13. Subscription
@Edith_H

14. Sunset
@Edith_H

15. Effective Feature Flagging
• What’s
the
right
level
of
flagging?
• Ambiguously
named
flags
• Misunderstood
flags
• Removing
flags
• Control
access
to
flags
• Visibility
to
non-­‐technical
users
• Logging
• Dependency
tracking
@Edith_H

16. Launch, control, and measure your features
Edith Harbaugh, CEO
edith@launchdarkly.com
@Edith_H
@LaunchDarkly LaunchDarkly.com