Manejar Feature Flags en Flujo de Desarrollo | GitScrum
Gestiona desarrollo con feature flags para creación, testing, rollout y limpieza. GitScrum coordina el ciclo de vida de flags entre equipos.
4 min de lectura
How to handle feature flags in development workflow?
Handle feature flags by creating tasks for each flag lifecycle stage: implementation, testing behind flag, gradual rollout, full release, and cleanup (flag removal). Use labels to track flag status (flag:active, flag:deprecated), document rollout plans in NoteVault, and schedule cleanup tasks to prevent technical debt from abandoned flags.
Feature flag lifecycle tasks
| Stage | Task | When |
|---|---|---|
| Creation | "Create new-checkout flag" | Sprint planning |
| Development | "Implement checkout behind flag" | Development |
| Testing | "Test checkout flag on/off" | QA |
| Rollout 1% | "Enable checkout for 1% users" | Release |
| Rollout 100% | "Enable checkout for all users" | Monitoring OK |
| Cleanup | "Remove new-checkout flag" | 2 weeks after 100% |
Feature flag labels
| Label | Purpose |
|---|---|
| flag:created | Flag exists, feature in development |
| flag:testing | Flag in testing environment |
| flag:rolling-out | Gradual rollout in progress |
| flag:100-percent | Fully enabled |
| flag:cleanup-needed | Ready for removal |
| flag:deprecated | Scheduled for removal |
Feature flag task template
FEATURE FLAG: new-checkout-flow
Created: 2025-01-15
Owner: @developer
Rollout Plan:
- [ ] Week 1: 1% of users
- [ ] Week 2: 10% of users
- [ ] Week 3: 50% of users
- [ ] Week 4: 100% of users
Monitoring:
- Checkout completion rate
- Error rate on checkout
- Support ticket volume
Rollback trigger:
- Error rate > 0.5%
- Checkout completion < 80%
Cleanup deadline: 2025-02-28
NoteVault flag registry
# Active Feature Flags
| Flag | Owner | Status | Created | Cleanup Date |
|------|-------|--------|---------|--------------|
| new-checkout | @alice | 50% rollout | 2025-01-15 | 2025-02-28 |
| redesigned-nav | @bob | 100% | 2025-01-01 | OVERDUE |
| dark-mode-v2 | @carol | Testing | 2025-01-20 | 2025-03-15 |
## Stale Flags (> 30 days at 100%)
- redesigned-nav: Should have been removed 2025-02-01
## Recently Cleaned Up
- old-payment-flow: Removed 2025-01-10
Preventing flag technical debt:
Common flag mistakes
| Mistake | Prevention |
|---|---|
| Forgotten flags | Cleanup tasks, registry |
| No rollback plan | Document in task |
| Untested flag off | Test both states |
| Complex flag logic | One flag per feature |
| Permanent flags | Expiration dates |