Report Offensive Message

Don't think of ISO9000 as a standard way to do things that you must follow to do your job. "Your ISO standards" are "yours" because they document what "you do and how you do it" What it is trying to do is say if you do it "this way" today then do itthat way tomorrow and ... This is why there is not a "boilerplate standard" ISO9000 is trying to get you to do a procedure the same way every time. When you release a system to production most places of any size require you to fill out some form or forms to document that you did this. In the ISO9000 world there would be a copy of that form in the standard and an instruction on how to fill it out and that is all. When you hire a new employee you can say read these procedures and you will know how we release software to production and also what types of reviews and testing are required before that point. You should always start writing your "standard" from where you are "today" and then modify it in the future to imporve your processes. It does not try to turn software development into a rigid production line process.