Why good teams rely on bad workarounds

UPcoming Panel discussion

Why good teams rely on bad workarounds

Messy workarounds aren’t a symptom of careless teams, but of delivery pipelines that aren’t fit for purpose. Here’s how to root out the unnecessary friction.

Francine Pilot, Steve Fenton, Simone Casciaroli and Ryn Daniels

Date & time

17:00

Register for the panel discussion

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

Even the most well-intentioned delivery pipeline can lead to unintended workarounds. You may have selected best-in-class tooling and defined best practices, but no two teams or projects are the same. When delivery pressure builds, teams find inventive ways to bypass systems that aren’t serving them, leading to increased rework and risk.

For engineering managers and platform engineers, the challenge is to identify where teams need more options and find ways to provide them without abandoning the appropriate constraints.

In this panel discussion, we’re lifting the lid on why and where the most common workarounds crop up in delivery pipelines, and the modern aspects of software delivery that enable you to stop them in their tracks.

Key takeaways:

The most common delivery workarounds and why they happen
Rooting out unnecessary sources of developer friction
Allowing more choice in tool selection while maintaining robust delivery practices