Do to varying opinions in the office and significant resistance from project managers (not from developers) I'm curious others deal with the end of QA/testing phase.
When a project is done with its testing phase (do to deadlines), does the company have a process for the
A. PM and QA work to create problem tickets or problem requests (whatever your company calls them) for legitimate qa defects?
B. Does the PM just call the phase over; disregard any open defects still outstanding in the project, passing the cost of fixing it to customer support or production support when the end user finds the issue?
C. Does your PM and QA manager present a list to the customer of the open defects (as of the deadline) and ask for sign off? And still does nothing with the defects presented to the customer (i.e. no problem tickets reported as fall out and no plans to fix it)?
D. Does your QA department create the list defects that are moving into production, present the list to the customer and create the problem tickets? Without the PM?
Personally, I have never experienced a PM group so disengaged and uncaring about what they are putting into a production environment. Some of that may be the our culture not tying quality into any projects success factors. I've almost always experienced some version of A.
Please share your opinions and experience.
"We may encounter many defeats but we must not be defeated."