vendredi 15 avril 2016

Highlighting of risk areas during working on a task

Some of software companies have a rule: every developer during working on a task have to highlight risk areas to tell QA engineers what parts of the system he's probably affected. In my opinion it could be useful to avoid bugs after release.

So my question is: has anyone heard about this practice? Does anyone have any articles on this point, or may be have any ideas how to find out what risk areas have to be hightlighted?

Aucun commentaire:

Enregistrer un commentaire