Skip to main content

10 statuses you should have in a Defect Life-Cycle


There are different approaches to achieve a proper Defect life-cycle solution with different theories and goals behind each one of them but from my experience most of the solutions that will have the following 10 statuses when implemented will have the better results in improving the final quality of the company’s product:

New
New status will be the first status for a freshly created Defect. This status should be reviewed by leading person like Development team lead or a QA manager and should be then assigned to a specific developer who will fix the problem.
From this status the Defect can become “Open” or “Awaiting Client’s Clarification”

Open/In-progress
Open status exists to emphasize that a specific Defect is in active state. This status means the some actual work is done related to this issue or that some investigation regarding this issue is happening.
From this status the Defect can become “Fixed” or “Won’t Be Fixed” or “Awaiting Client’s Clarification”

Postponed
In case that some constrains of the current release preventing the development department from fixing a specific Defect this Postponed status is used to symbolize the fact that this issue will be fixed in the future.
From this status the Defect can become “Open” or “Won’t Be Fixed”

Awaiting Client’s Clarification
Awaiting Client’s Clarification status indicates that the issue raised by this Defect is requirement related and requires client feedback as whether it is an actual problem or not.
From this status the Defect can become “Open” or “Won’t Be Fixed”

Fixed
Fixed status is self explanatory and represents the fact that the Defect had been fixed.
From this status the Defect can become “Re-Open” or “Fixed – Postponed” or “Fixed – Closed”

Fixed – Postponed
Fixed – Postponed status existence is to provide the option to mark a Defect as fixed but emphasize the fact that it had not been verified by QA in the last test cycle. As a common practice this status should not be used and it should be kept for extreme situations only when because of some constrain this unusual situation happened.
From this status the Defect can become “Re-Open” or “Fixed – Closed”

Fixed – Closed
Fixed-closed status is to communicate the fact that a Defect that had been fixed by development had been verified by QA as well and the fix is fully accepted

Won’t Be Fixed
Won’t be fixed status is used to categorized two types of Defects: those that are not actually a Defect and had been created by misunderstanding of client’s needs, and those that represent a problem that to costly to fix when compared to the benefit of the actual fix.
From this status the Defect can become “Re-Open” or “Won’t Be Fixed – Closed”

Won’t Be Fixed – Closed
Won’t Be Fixed-closed status is to communicate the fact that there is an agreement from QA side with the fact that this Defect shouldn’t be dealt with, and no more future work will be invested in this issue.

Re-open
Re-open status come to emphasize that it isn’t the first time that this Defect is reaching the development. This status can be a result of a “Fixed” status when the fix had not been complete, or it can be a result of “Won’t Be Fixed” status when there is a disagreement from QA side that this Defect is not important enough.
Note: Re-opening a Defect it is critical move and it should always be done with detailed comments explaining the reasons for it.

Comments

Popular posts from this blog

Story Points estimation for Scrum with Fibonacci vs Shirt Sizes vs Linear - 7 minute guide

It is all began long time ago when Development Teams were constantly asked to provide estimate and they were having a hard time to properly face the task. Let's admit it, there are so many things that can change, happen, and simply go wrong during the development process that one can hardly expect a proper estimation of hours for each task. That why a relative estimation with Story Points came along. Story Points Estimation Its a different way to estimate the effort of the Scrum Development Team with-in Agile methodology, which means that instead of estimating hours of work the team estimates each effort relatively to other efforts in the project. Let's assume that a developer knows that specific 'Task 1' is much harder than another 'Task 2' it is hard for him/her to quantify that harder feeling in hours of additional work but it is possible to say that it much more work. This situation is being address by Story Points when each story point is

7 Most Popular Test Types in Software Testing

Today we are going to return back to basics of software testing and discuss the 7 most popular test types that are being used in every software testing effort. Those different test types cover all the levels of the software to make sure that the final result matching the expectations from every possible angle. Here is our list: Unit testing Smoke testing Regression testing Functional testing Integration testing User Acceptance Testing Performance Testing Now let’s have a deeper dive into each one of those by using a simple example of an imaginary system that was created in order to manage warehouse activity including shipments, inventory and goods receptions from suppliers. Unit Testing This type of testing is usually performed by the developers and is covering the very basic development component. In this test developers are testing the straight forward functionality of a functional piece of code to make sure that it is performing according to th

What is the velocity of an Agile scrum methodology?

Let's discuss some of the important measurements in Agile, and that is the Velocity of the Scrum team work. Based on Wikipedia definition Velocity is " ...the rate of change of its position with respect to a frame of reference and is a function of time...", which when transferred to the scrum world can be summarized as: The amount of work that the scrum team completed in a single measure of time - in a sprint. How we Calculate Velocity? Velocity is actually a very simple to calculate, it is done but totaling the number of story points of fully completed user stories from the sprint backlog. So if a current sprint included 4 user stories: 2 with 8 story points each, one with 3 story points and one with 32 story points. and by the end of the sprint the 32 one was not fully done the velocity calculation will be: 8+8+3=19 Note: the 32 story points are not part of the velocity calculation as this user story was not completed. What Velocity is used for? The v