Distinguish release, experiment, permission and operational flags and design an appropriate lifecycle for each.
Information & Communications Technology
Feature Flag Management and Progressive Delivery Techniques
Manage feature flags and progressive delivery pipelines to ship changes safely through canary releases, dark launches and controlled rollbacks.
🗓️Duration5 training days
📚Content4 modules · 8 sessions
🎓On completionAccredited attendance certificate
About the programme
Course Overview
Deploying code and releasing a feature are two different decisions, and treating them as one is what forces teams into risky big-bang launches that can only be undone by another full deployment. This course teaches feature flag management and progressive delivery as the practice of separating those decisions: shipping code continuously while controlling exposure through flags, percentage rollouts and targeted user segments. Participants design flag lifecycles from creation through cleanup, distinguishing release flags, experiment flags, permission flags and operational kill switches so that a flagging system does not collapse under its own accumulated debt. Sessions cover canary release patterns that expose a change to a small slice of traffic before wider rollout, dark launches that exercise new code paths without user-visible impact, and blue-green deployment for instant rollback of infrastructure-level changes. The course also addresses monitoring and automated rollback triggers tied to error rates and business metrics, and the governance needed to stop flags from turning into permanent, undocumented conditional logic scattered through the codebase.
Expected Learning Outcomes
Design canary release strategies that expose changes to a controlled percentage of traffic before full rollout.
Implement dark launches that exercise new code paths in production without visible user impact.
Configure blue-green deployment patterns that enable instant rollback of infrastructure-level changes.
Set automated rollback triggers based on error rate, latency and business metric thresholds.
Govern flag creation and retirement to prevent flag debt from accumulating in the codebase.
Design experimentation flags that support reliable A/B testing without contaminating other rollouts.
Who Should Attend
Software engineers implementing feature flags in application codebases.
Release managers coordinating progressive rollout of new features.
Site reliability engineers responsible for rollback and incident response.
Product managers running experiments and staged feature rollouts.
Engineering leads establishing feature flag governance standards.
DevOps teams building continuous delivery pipelines with progressive exposure control.
Course Modules
Select any module to see its sessions and points.
01Feature Flag Types and Lifecycle
2 sessions · 8 points
Session 1Classifying Flags by Purpose and Lifespan
- Distinguish release flags, experiment flags, permission flags and operational kill switches by intended lifespan.
- Assign ownership and expected retirement dates to each flag at the point of creation.
- Design naming conventions and metadata that make flag purpose clear to any engineer reading the code.
- Separate flag configuration from application code so changes do not require a redeploy.
Session 2Managing the Full Flag Lifecycle from Creation to Retirement
- Track flag status through creation, rollout, full release and scheduled retirement stages.
- Set up automated reminders that flag stale flags left active long after their purpose is served.
- Remove flag-related conditional logic from the codebase once a rollout is complete and stable.
- Audit the flag inventory periodically to prevent undocumented flags from accumulating as technical debt.
02Progressive Rollout Patterns
2 sessions · 8 points
Session 1Canary Releases and Percentage-Based Rollouts
- Design canary release plans that expose a change to a small percentage of traffic before wider rollout.
- Select canary cohorts that represent real user diversity rather than only internal or low-risk traffic.
- Define rollout stages with explicit go or no-go criteria at each percentage increase.
- Coordinate canary rollout timing with on-call coverage and monitoring readiness.
Session 2Dark Launches and Segment-Targeted Exposure
- Implement dark launches that exercise new code paths in production without user-visible changes.
- Target flag exposure to specific user segments, regions or account types for controlled testing.
- Use shadow traffic techniques to validate new backend logic against production load safely.
- Coordinate cross-team dependencies when a dark launch touches shared services or data models.
03Deployment Patterns and Automated Safety Controls
2 sessions · 8 points
Session 1Blue-Green Deployment and Infrastructure-Level Rollback
- Design blue-green deployment pipelines that allow instant traffic switch-back on failure detection.
- Coordinate database schema changes so they remain compatible across both deployment environments.
- Plan traffic-shifting mechanics between environments using load balancer or service mesh routing.
- Rehearse rollback procedures regularly so the team can execute them confidently under pressure.
Session 2Automated Rollback Triggers and Release Monitoring
- Define error rate, latency and business metric thresholds that trigger automatic rollback.
- Instrument releases with real-time dashboards that make rollout health visible during each stage.
- Set alerting that distinguishes a genuine regression from normal traffic variance during rollout.
- Document post-rollback analysis procedures that feed lessons back into the release process.
04Experimentation and Governance
2 sessions · 8 points
Session 1Designing Reliable A/B Testing on Top of Feature Flags
- Design experiment flags that assign users consistently to control and treatment groups.
- Prevent overlapping experiments from contaminating each other's measured outcomes.
- Define statistical significance and minimum sample size requirements before drawing conclusions.
- Separate experimentation flags from release flags to avoid entangling their independent lifecycles.
Session 2Flag Governance and Organisational Standards
- Establish organisation-wide standards for flag naming, ownership and maximum lifespan.
- Set approval workflows for high-risk flags that control critical business functionality.
- Train engineering teams on avoiding excessive flag nesting that makes code paths hard to reason about.
- Review flag governance metrics periodically to keep the practice sustainable as the codebase grows.
What the participant receives
4 course modules
A structured syllabus
8 training sessions
across 5 days
32 detailed points
Applied, detailed content
Accredited attendance certificate
On completing the programme
Complete your registration
We will contact you within one business day to confirm.
Ready to start?
Reserve your seat and start building the skill.