mirror of
https://github.com/Unleash/unleash.git
synced 2025-10-27 11:02:16 +01:00
e197934fa4
I'm adding a Feature Flag Migration tutorial written by Customer Success to the docs. The content should live in the Topic Guide section Topic Guides Feature Flags Migration Best Practices index page with subpages for * Define scope * Make business case * Planning * Execution * Onboarding users --------- Co-authored-by: Thomas Heartman <thomasheartman+github@gmail.com> Co-authored-by: Gastón Fournier <gastonfournier@gmail.com> Co-authored-by: Gastón Fournier <gaston@getunleash.io> Co-authored-by: Mark Fulton <128738155+markunl@users.noreply.github.com> Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
17 lines
1.0 KiB
Markdown
17 lines
1.0 KiB
Markdown
---
|
||
title: Make the business case for feature flag migration
|
||
---
|
||
|
||
Once you have scoped your migration, you need to make a business case. Even the most well planned migrations take effort, meaning time, money, and energy dedicated to a project. If you don’t have the proper buy-in, you risk being under-resourced or worse, being unable to complete the migration at all.
|
||
|
||
When building a business case, you want to be clear on what pain the feature flag migration is solving and the happy end state once the migration is complete.
|
||
|
||
To structure your thinking, ask yourself:
|
||
|
||
* What practices related to feature deployments, debugging and rollbacks are overburdening teams today and driving down productivity?
|
||
* What specific deficiencies are there in the current platform
|
||
* What business outcomes are you looking to drive?
|
||
* After the migration, what does "better" look like?
|
||
|
||
Use our [Feature Flag Migration template](https://docs.google.com/spreadsheets/d/1MKc95v7Tc-9tznWMDVSy2vvmVJTvOFLRVZpx1QrL-_U/edit#gid=996250264) to fill in details about your business case.
|