Feature Management

Recently I was reading about Feature management and basis on my understanding, If multiple teams are releasing new features every release and merging code to Original Codebase, It is worth trying a Feature Management tool.

Why Feature Management:

Control feature releases

o??Reduce the risks associated with rolling out a?new feature using feature flags

• §?Find bugs;
• §?Catch performance issues; and
• §?Collect user feedback.

o??Test in production by turning it on only for internal?users

?

o??Decouple deployment from release

Enabling the features for specific client and user groups

o??Features can continuously deployed to the application, but they would only be released when completely tested (with one client/User group)

o??OR if required, would be available for only specific group/s.

• §?Enable feature experimentation – giving leadership data to decide if feature should be part of product et all.

Enable progressive delivery

o??Keep adding features to their solution without actually deploying them.

o??Decouple development lifecycle from its efforts on driving innovation.

• §?Allocate separate IT resources for both functions. Feature team could work on driving innovation, whereas other team can go into "keeping things running," where it typically goes.

o??Enable A/B for software products

Which Tool to use:

There are Many Tools available to consider basis cost and requirement:

Like LaunchDarkly , Optimizely Web Experimentation,?ConfigCat, and?Firebase

LaunchDarkly provides a feature management platform that enables DevOps and Product teams to use feature flags at scale. This allows for greater collaboration among team members, and increased usability testing before full-scale feature deployment.?

We can use LaunchDarkly to help hide incomplete features from end users. This allows us to deploy code to production more often, which reduces code conflicts and leads to a healthier codebase

LaunchDarkly is great when you need to deploy frequently for teams that are experiencing growing pains because there are more and more developers beginning to contribute to the same code base. It is less important when you have very few users or very few developers. It is also less important when you deploy infrequently, because you are more likely to deploy fully complete and tested code to production in that case.

Similarly other tools also have great features to assess and utilize.

Thank You!