wumpus wrote on May 7
th, 2012 at 10:45am:
Just out of curiosity, does anybody work in an industry where QA (software in particular) has any real say over what get shipped and when it will ship (by virtue of tests passed, not in meetings planning the schedule although they tend to be ignored anyway)?
I do. ( both Hard and Soft )
But well, Telco is a bit special. Despite all the IT not-processes we are getting, we still live with our old industry processes. We have reduced Software QA from a 9 Month thorough
Check it all marathon ( before allowing the customer to play with it ) to a weak 2 month
Make sure it does what we are selling it for speed run.
Then the customer takes over and does his own QA for a few weeks... Usually on parts of the design that haven't been tested.
I did some QA for a project a few years ago and I personally said the project was a no go on a live system until a given bug was solved.
I did the upgrade of a system last year, and we barely escaped the rollback by doing double shift to recover and fix a set of data that has been missed by the upgrade script.
Analysis showed that everybody ( including the customer ) missed to make tests on that data set in the various QA rounds... Except for the last QA round that happened just before we put the updated system back in service.
We still have ( and sell ) Telco equipments where a system restart ( or a software crash that causes a partial system outage ) is an event that
shall not happen, so QA has to be thorough.
and to answer on the ISO thingie : ISO 9001 ( and most of the others ) is a joke.
ISO 9001 Certification just says that you have a quality process in place and that you're adhering to that quality process.
Your quality process can be :
do nothing about quality. You'll still get certified as long as you adhere to that do nothing.