Tip 3: If you need it, check it in.
If you can generate it, then don't check it in.
- pick an SCM
- learn how to use it
- generate a single-page quick-start guide that shows how to use the system for common operations
- show the system to your team and make sure everyone is comfortable with it
- import your code and supporting files
- start keeping all your files in SCM
- Are you actively using the system?
- How long would it take to get a new machine up and running?
- Can you perform SCM operations quickly?
- Are you backing up the SCM's repository?
- Can you check out the entire project?
- Can you look at the differences between local edits and the code in SCM?
- Can you view the history for a specific file -- who changed this file when did they do it?
- Can you update your local copy with other developer's changes?
- Can you commit your changes to the SCM?
- Can you remove the last changes you pushed into SCM?
- Can you retrieve a copy of the code tree as it existed last Tuesday?