Feature Flags Solution Validation
What’s this issue all about?
Feature flags user journey
Who is the target user of the feature?
Users of feature flags Developers (internal gitlab can be used here) Release managers
What questions are you trying to answer?
- What should be the flow of creating/editing/archiving feature flags?
- What are the strategies that we need to support?
- Will users manage feature flags via the UI or only via API and markdown?
- What info do we need in a feature flag dashboard?
- Are users interested in an automatic disablement of feature flags (such as once it hits a certain percent)
- A/B testing - how popular is the demand for this?
- Who should gain permissions for toggling the feature flag?
- Connection between environments and feature flags
Core questions
Additional questions
Is it worthwhile to check an alternative approach of acquiring a company that does this instead of delevoping from scratch?
What hypotheses and/or assumptions do you have?
Feature flags are used primarily by developers and DevOps engineers. Most users will user markdown and/or chatOps to turn flags on/off via merge requests. Feature flags cause tech debt and someone needs to manage them and remove the un-needed feature flags
What decisions will you make based on the research findings?
The design of the feature flags management priority of the feature flags development issues
When do you need this research to be completed? (Milestone or date)
12.7
Links
Phase 1 of interviews - https://gitlab.com/gitlab-org/uxr_insights/issues/695
Phase 2 of interviews/usability - &2511
Edited by Mike Nichols