Have a look at the following - I don't have a copy but apparnetly it's quite good


http://www.hentzenwerke.com/catalogavailability/essvss.htm


>To all,
>
>for a project we have a pool of programmers. We are using VSS at this moment but we are just using it in a very simple form. We want to start bringing procedures into place so we can have some grip on our sources, changes and releases. Does anyone have any guidelines on how to start developing in teams and how to start with some form of release management with VSS? I looked on MSDN but there it only tells you that VSS is a great tool. It doesn't tell you bow you should arrange things like this. I'm sure that what we are looking hasn't been thought of before ;-)
>
>Any help is greatly appreciated.
>
>Regards,
>
>Ron Brahma