Defect Identification & Management Practices in Software Development - Part1

| by Shane Hastie Follow 25 Followers on Jan 21, 2015 |

InfoQ's research widget has been deprecated. It should continue to work however, and we hope to relaunch it at some point in the future.

This research item is one of two that look at the defect identification and management practices in software development.

A defect is behaviour that is in some way unintended in a software product – the visible evidence of a mistake made somewhere in the development process, perhaps a requirement stated incorrectly (or left out), a design that overlooked how something should be done, or a coding error.

Almost all software development approaches incorporate processes for tracking, recording, measuring and resolving defects.

The intent of this research item is to identify the team organisation/structure approaches and defect identification & tracking practices without explicitly ranking their effectiveness against one another – once we have a picture of which techniques and practices are in use in real world development teams we will drill deeper to identify the effectiveness of the different techniques in use.

This first research item looks at the structure of QA/test teams in organisations and the way defects are reported & recorded.

The second item will look at how defects are addressed and tracked.

Team organisation/structure and defect recording

Topics to Rank

  • Quality part of development team
  • Independent quality team
  • Independent quality and test team
  • Quality and CM combined
  • Assign unique defect ID
  • Record date identified
  • Record iteration found
  • Record iteration resolved
  • Record release found
  • Record defect type (requirements, design, code, test)
  • Record defect priority
  • Record defect urgency
  • Record defect category (logic, data, etc.)

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Thats IT??!? by Chris Turner

This was not enough to warrant publishing

Re: Thats IT??!? by Shane Hastie

Hi Chris

We are a bit limited by the tool, but this is just the first of a few research pieces which will hopefully combine to give a picture of what the state of practice is in defect identification, management, resolution approaches and other aspects. The combined results will be consolidated into an article which we hope will be of value to the community.


Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

2 Discuss

Sponsored Content

Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you