#Defect process in agile code#

Where I’m sure no one would raise a bug for a code review issue, or a unit test failure?Īs with processes in general, whatever works best for you is the best and it sounds like you have thought about your process. We also feel it follows a similar model to other US QA steps, such as Unit Test or Code Review. We find this a much faster process than raising a separate US/Bug for every issue, which would then need to be prioritised by the PO and either brought into the sprint or put on the backlog (which would then block the current US in this sprint). So can capture metrics for issues found, if we need to. In Jira we can track that a US has moved left on the board, from “Ready For Test”, rather than right. If we find a separate unrelated bug we will raise a bug which will be prioritised by the PO for backlog/current sprint.Where the developer will continue to work on their US. Finally setting the US back to “In Progress”. We will discuss the issue with the developer, then in the comments of the US will detail the issue seen and steps taken to replicate. A User Story( US) moves across the sprint board from “In Progress” to “Team QA” (= code review) to “Ready For Test”.ĭuring the test cycle if an issue with implementation directly related to the US is found. We operate a 2 week sprint cycle not cam-band. I’d like to just check the sanity of our current Agile process with a larger audience.

How to manage Issues/Defects relating to the User Story being tested?įollowing on from a previous post also titled “Issue/Defect Management” which asked a broader waterfall/agile question.