Fail fast, learn faster: Real lessons from failed software releases

Discover real lessons from failed software releases. Learn to manage tech debt, improve communication, and ensure successful rollouts with insights from industry experts.

Featuring P.A. Masse , Mirella Batista , Ryn Daniels , Leemay Nassery

November 26, 2024

On demand video

Login or join LeadDev.com to view this content

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

We have linked your account and just need a few more details to complete your registration:

First name Last name Job title Company Country

Terms and conditions I agree to the LeadDev.com terms and conditions of use

Create a password

More like this

Releasing software is a critical milestone for engineering teams, but it doesn’t always go to plan.

No developer wants to release faulty software. In many cases, we can trace failed releases back to resourcing problems and unrealistic time constraints, resulting in corners being cut, bugs being overlooked and a breakdown in communication between key teams.

In this panel, we plan to give you a ‘peek behind the curtain’ into real-life examples of software release failures, how they occurred, and what could have been done differently.

Register now to learn:

What a ‘success release’ looks like to different teams
Ways to manage tech debt incurred by feature management processes
Build vs buy – which tooling is best for detecting issues during feature-flagged rollouts?
How to conduct thorough and constructive postmortems