Speed of software delivery is important, but it shouldn’t come at the expense of quality. If you want to avoid bugs, difficult rollbacks, or even a costly outage, you need a process that introduces new features in a controlled and reliable manner.
In this Deep Dive, you’ll learn why the old adage of moving fast and breaking things isn’t fit for purpose, why it might be time to re-evaluate the role of QA, and what successful feature management really looks like.
Deep Dive
In partnership with
How to grow and scale your feature management process
Engineering leaders walk you through secure and efficient ways to manage the release of your feature that will save developer time, as well as avoid unwanted side effects of releasing new software into the world.
Why you shouldn’t move fast and break things
Chris Stokel-Walker explores the history of the phrase – and the limitations of this approach in modern software delivery.
The quickly evolving role of QA
Saurav Sharma, Engineering Lead at Trivago, argues that we can address tensions between speed and quality by viewing QA as an enabler, rather than a gatekeeper.
Unlock your engineering velocity with data
The best way to empower and incentivize your engineers, is by showing them the impact they’re having on the business – says Tore Hanssen, Engineering Manager at Statsig.
Are you looking to foster a culture of experimentation in your teams?
Now it’s possible to ship, test and analyze new features – all on one platform.