I've gotten several questions lately about how to deploy an ASP application to a web server. Not that this is a best practice, but here's how I work on my own ASP sites:
1) On my home server, I set up a web site on a different port, like 7878 or some other random number. I then set up the appropriate directory structure. I give the site its own port number so that I can use absolute page references (like /include/common.asp) and I don't have to worry about what else is on the site.
2) I do my development on this test server, including any testing. If I'm developing COM components for the site, they get registered on the test server.
3) When the application is ready to go live, I copy all the files from the test server to the production server. If I'm using any COM components, those have to be registered on the production server.
That's really all there is to it. You can use as many development/test servers as you need. For instance, you may want to set up a separate server for a testing team. If it's not that big of an application, you could just set up another web site on a different port number. The only conflict would be if you are using COM components. If so, you should probably set up your environments on different physical machines. That will let one team's components be separate from any others on the machine.