I have been asked to define a change control procedure for my department. I am the only QA person, amid about 7-8 software developers. I feel funny trying to write up a change control procedure document when I have no idea what they do day to day. Is there some standard change control procedure document I could borrow from?
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by jstrazzere: You should probably sit with the developers and learn what they do from day to day before you write a plan to change it.
What questions should I ask them? What am I looking for?
Change Control is basically a component of Configuration Management. The way we term Change Control is "How, when and what are we doing to change the production system?" Configuration Management goes a bit further than that by basically controlling the entire configuration right down to the source code and in some cases the 3rd party code. Is it truely a Change Control procedure that is being developed and if so, it shouldn't really require knowledge of the day to day operations of development but how to best ensure approval and implmentation of a change to the production system.