Scaling Feature Flag Management for Better Progressive Delivery [Webinar]
This webinar covers considerations for scaling feature flag management with an emphasis on how to reduce the technical debt caused by feature flags.
Join the DZone community and get the full member experience.
Join For FreeThis webinar has already occurred, but you can access the free on-demand recording here.
The concept of "progressive delivery" using feature flags has rapidly grown in recent years as the "new standard" in DevOps excellence, and for good reason. The concept of using feature flags to decouple deployment from release to deliver "progressively" expands the principles of continuously improving software directly into production with real users -- in a safe, controlled way. Further, feature flags provide a wide variety of safety and speed improvements within software delivery, effectively "supercharging" CI/CD in new ways.
However, achieving these software delivery benefits at scale doesn't come without downsides. Complexity can grow in testing, accrual of technical debt, and general visibility and governance of feature flags across CI/CD toolchains.
Join us on May 18th and we'll cover the considerations for scaling feature flag management with an emphasis on how to reduce the technical debt caused by feature flags. We'll also look at best practices for testing flags and for creating strong governance and approval practices.
It IS possible to scale feature flags across even complex enterprise software delivery environments, and you'll leave this webinar with a better understanding of how to scale feature flags to do so.
Date & Time
Wednesday, May 18, 2022 at 1pm EDT | 10am PDT
Presented by
Nick Rendall, Sr. Product Marketing Manager, CloudBees
Jamie Melnyk-Perrin, Product Manager, CloudBees
Hosted by DZone
Can't join us live? Register anyway and you'll receive the on-demand recording to watch at your convenience!
This webinar has already occurred, but you can access the on-demand recording here.
Opinions expressed by DZone contributors are their own.
Comments