When DEV or CR request for the impediment - it is slowing down the whole process. The fact is that to register impediment you don't need to clarify what exactly you are waiting for. I feel like this decreases the quality, as it is not clear what are the dependencies between tasks and in which order they should be finished.
Thus, there should be a QA rule that sounds something like this:
Impediment registered in the ticket has clear link on connected issues.
The text was updated successfully, but these errors were encountered:
When
DEV
orCR
request for the impediment - it is slowing down the whole process. The fact is that to register impediment you don't need to clarify what exactly you are waiting for. I feel like this decreases the quality, as it is not clear what are the dependencies between tasks and in which order they should be finished.Thus, there should be a QA rule that sounds something like this:
The text was updated successfully, but these errors were encountered: