CAPM Practice: Validate requirements through product delivery

Feature toggles allow teams to deploy code for a new feature while exposing it only to selected user groups. This enables controlled requirements validation with real users before full rollout — if validation reveals issues, the toggle is turned off without a deployment.

**Why not B:** A prioritization tool for toggling features between must-have and nice-to-have status describes requirements prioritization, not a feature toggle. Feature toggles are technical mechanisms in code that control feature visibility at runtime, completely separate from prioritization frameworks.

**Why not C:** A toggle switch on a requirements document indicating feature completion is a tracking mechanism, not a feature toggle. Feature toggles are implemented in the software itself, allowing features to be enabled or disabled in production without redeploying code, enabling staged validation with real users.

**Why not D:** A meeting mechanism for toggling between discussion types is a facilitation technique, not a feature toggle. Feature toggles are technical infrastructure that controls which features are visible to which user segments, supporting controlled rollouts and real-world requirements validation.