Practice feature flag cleanup vocabulary: stale flags, technical debt, flag lifecycle management, 100% rollout cleanup, and flag cleanup sprints.
0 / 5 completed
1 / 5
'We have 47 flags older than 6 months.' These are referred to as _____ flags.
'Stale flags' are feature flags that have not been updated or removed after their purpose was served, accumulating as technical debt in the codebase.
2 / 5
'The flag has 100% rollout — _____ it.' What should be done with a fully rolled-out flag?
When a flag is at 100% rollout and has been stable, the flag and its conditional code should be removed from the codebase — it's no longer needed.
3 / 5
What is a 'flag cleanup sprint'?
A flag cleanup sprint is a focused engineering effort to identify and remove stale, fully-rolled-out, or abandoned feature flags to reduce codebase complexity.
4 / 5
'Stale flag technical _____' — what problem does flag accumulation cause?
'Technical debt' is the correct term — accumulating stale flags makes code harder to read, test, and maintain, and can hide conditional logic bugs.
5 / 5
Which concept describes the full lifecycle of a feature flag from creation to removal?
'Feature flag lifecycle management' covers the entire flag journey: creation, rollout stages, full enablement, and eventual removal from code.