We are working pretty tight with our QA department. Yes, we have some well-documented work procedures but some times I feel that they are too well-documented. After all, we are lazy; We want something easy to see, easy to read & easy to do.
I thought it will be better to document our relations (Development team with QA) in a simple flow diagram:
Bug life cycle – in the eyes of a programmer.ppt (55.5 KB)
I’ve added a step: what should I (the programmer) do if I can’t reproduce the bug ?
Maybe it will help you as well.