#DEFECT PROCESS IN AGILE SOFTWARE#

In this scenario the user story should go back to the developer to resolve the defect and then be re-tested until the defect is fixed. The first scenario is what I’d expect to be the norm for most Agile delivery teams running any methodology that is delivering new features.

Scenario: A user story is in the process of being delivered and while being tested internally in the team a defect is discovered. Lots of teams have very different processes because of how they are constrained by the wider organisation they are working within but hopefully, whatever the wider context, there should be something here for you. Whether you encounter these scenarios or not in your situation depends upon how widely and deeply your team has adopted Agile principles and processes. I’m going to cover three different scenarios. The first of which is: “How do you run defect management on Agile projects?” This lack of clarity and therefore certainty crops up again and again when I’m teaching people about the various Agile methodologies that exist so I thought it would be worth putting down answers to some of the more common questions.

#DEFECT PROCESS IN AGILE SOFTWARE#

However, in the world of Agile delivery we drive accountability for the overall process of delivering working software to the delivery team as a whole and not a lot is said about how, specifically, the team should operate. Defect management used to be a very well defined, well understood and tightly controlled, all be-it wasteful, process.

Defect process in agile