Date & time
17:00 BST
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 how to:
- 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
Featuring:
In partnership with
