I’ll never understand teams that manage bugs instead of fixing them

TL;DR

Teams should focus on fixing bugs as soon as they are found instead of managing or prioritising them in backlogs or meetings. Delaying bug fixes leads to bigger problems and undermines the goal of delivering working software. Development managers should ensure their teams address defects promptly rather than letting them accumulate.

1 May 2025
Written by Martin Hinshelwood
1 minute read
Practice Engineering Excellence
Table of Contents
Comments
Comment
Feedback
` LinkedIn WhatsApp Twitter Facebook Email
Subscribe

I’ll never understand teams that “manage” bugs instead of just fixing them.

A bug backlog? Why. Just fix them.

A meeting to discuss bug prioritisation? Stop it. Just fix them.

A ticket that’s been sitting in “QA” for weeks? Absurd. Just fix it.

Here’s the deal: Known defects are holes in the ship. You don’t argue about whether to patch them while the water pours in. If a bug is found, it gets fixed. If it’s too big, escalate it and prioritise the fix. The longer you wait, the worse it gets.

Agile is about working software. Not half-working software with a spreadsheet full of problems you hope to deal with someday.

How does your team handle bugs? Are you fixing them or just shuffling them around?

Smart Classifications

Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.

Table of Contents
Comments
Comment
Feedback
` LinkedIn WhatsApp Twitter Facebook Email
Subscribe

What to read next

Signal Product Development Product Management

Building the wrong thing is worse than fixing a bug

Most features don’t deliver value. Short feedback loops and real user input help teams avoid wasted effort by ensuring they build what users …

Read article
Signal Scrum Product Development

Agile and Scrum are often misunderstood

Agile and Scrum expose underlying team and workflow issues, helping organisations address real problems rather than masking dysfunction with …

Read article
Signal Engineering Excellence Technical Leadership

There no such thing as "good" technical debt

Technical debt always harms productivity and system stability. Ignoring it leads to inefficiency and risk, making it essential to address …

Read article
Signal Product Management

A bloated backlog is not a sign of good product management

A cluttered backlog signals poor product management, causing confusion and lost focus. Keep backlogs lean to highlight priorities and drive …

Read article
Signal Leadership Scrum

Why compromising on software quality is a leadership decision

Compromising software quality is a leadership choice, not a team one. Lowering standards carries business risks that should be openly …

Read article
Article Engineering Excellence

Avoid the Bug as Task anti-pattern in Azure DevOps

Explains why treating bugs as tasks in Azure DevOps is an anti-pattern, its impact on transparency, quality, and planning, and offers …

Read article