Skip to content


Quality management is crucial in software development, yet it’s often overlooked or misunderstood. Here are are some tips for managing quality effectively in a software practice.

1. Defect Tracking: The Cornerstone of Quality Management

What is a Bug?

A bug is a ticket detailing a specific issue in the software. It includes the problem’s description, reproduction steps, and impact but not the solution.

Why Defect Tracking Matters

Surprisingly, many development teams neglect defect tracking, citing various excuses. However, the absence of a robust defect tracking system leads to lower quality outcomes. By ignoring bugs, teams are essentially turning a blind eye to potential improvements in their software.

2. Triage: Organizing Chaos

The Art of Bug Triage

Bug triage involves assigning, prioritizing, cleaning up, categorizing, and deduplicating bugs. Establishing a standard for classifying the severity of bugs (high/medium/low) streamlines this process.

The Importance of Triage

Proper triage enables a high-functioning organization to adapt to external stressors, reorganizations, or feature cuts. Ignoring the triage process is not an option unless your team operates in a static, unchanging environment (which is rarely the case).

3. Defect Investigation: Digging Deeper

Reproduction and Analysis

Reproducing a bug is key to understanding and fixing it. This process often requires translating vague user reports into concrete technical issues. Investigating the frequency and user impact of bugs is also crucial.

Engineering Rigor in Bug Management

Applying engineering rigor to bug investigation ensures that your backlog is not just a list of problems but a roadmap to improving your software.

4. Focus: Advocating for Quality

Quality as a Dedicated Role

While quality should be everyone’s responsibility, having team members specifically focused on it is vital. This ensures that there’s a voice in your team advocating for quality over velocity, balancing the two for optimal results.

5. End-to-End Testing: Owning the System

The Challenge of Architectural Complexity

Modern software architecture aims to keep teams and applications manageable, but this often leads to gaps in ownership of the overall system. End-to-end testing falls by the wayside, deemed too challenging by many teams.

The Need for Comprehensive Testing

End-to-end testing is essential for ensuring that all parts of your application work together seamlessly. It’s a critical step that shouldn’t be overlooked, regardless of its complexity.

Page last modified: 2023-12-27 15:35:57