---
title: "Feature flags | Skills We Assign For | Azendo"
description: "Feature flags — decoupling release from deploy, flag debt, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/feature-flags/"
---

[Skills](https://azendo.co/skills/) CI and delivery 

# Feature flags.

Feature flags decouple deployment from release: code ships disabled and is enabled by configuration, for specific users, percentages or environments, and can be turned off without a deployment.

## Where Feature flags fits on a long engagement.

Separating deployment from release changes how a team works. Incomplete work can be merged behind a flag rather than living on a long branch, which removes the painful integration that long-lived branches guarantee, and a problematic feature is disabled in seconds rather than rolled back.

Flag debt is the cost nobody plans for. Flags accumulate, each one doubling the notional paths through the code, and a codebase with two hundred stale flags has a combinatorial set of states nobody has tested and nobody dares remove.

## What an assigned team does with Feature flags.

Removal has to be part of the process rather than an intention. A flag needs an owner and an expected removal date at creation, or it stays forever — and the cleanup is never anybody's priority.

Holding that discipline across years is exactly what a standing assignment does, and what it covers is set out in [how the monthly fee is built](https://azendo.co/pricing/).

## What we use Feature flags for.

* Merging incomplete work safely Trunk-based development without long branches and painful integration.
* Disabling a feature without deploying Seconds to turn something off rather than a rollback.
* Flags removed on schedule An owner and a date at creation, because cleanup is never prioritised otherwise.

## How Feature flags capacity is assigned.

Delivery practice is assigned inside development capacity, with flag removal treated as part of the definition of done.

## Industries that ask for it

* [SaaS and technology](https://azendo.co/industries/saas-and-technology/)

## Related in ci and delivery

* [GitHub Actions — skill we assign for](https://azendo.co/skills/github-actions/)
* [Jenkins — skill we assign for](https://azendo.co/skills/jenkins/)
* [GitLab CI — skill we assign for](https://azendo.co/skills/gitlab-ci/)
* [Fastlane — skill we assign for](https://azendo.co/skills/fastlane/)
* [Codemagic — skill we assign for](https://azendo.co/skills/codemagic/)
* [TestFlight — skill we assign for](https://azendo.co/skills/testflight/)
* [App Store Connect — skill we assign for](https://azendo.co/skills/app-store-connect/)
* [Play Console — skill we assign for](https://azendo.co/skills/play-console/)

## Tell us what your roadmap needs Feature flags for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)