Ha, you think you're advanced because you have SCM and a CI system? Let me tell you that's amateur hour when it comes down to it.
A lot of companies do the minimum required, because that's all it really needs. If it works, and you get good reproducible releases without major effort, then there's nothing that needs to be fixed. The last thing you want to do in such circumstances is start to 'fix' things, especially when it comes to taking admin resources away from their work to set up and administer your new servers and build systems.
However, some companies require a bit more stringent systems in place, once that not only do the build, but control the requirements all the way through to the deployment via test plans and test results, taking in code review, workflow-style checkin procedures and team-leader designated work package management. That's real configuration management, and be damn glad you don't have to work in that kind of environment!
I've worked at a few companies, and I can't think of any that didn't have some form of SCM. Some of them were more comprehensive than others, but all of them had a system that worked well for them, even the ones that used VSS.