Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home/ekleus/ekle.us/inc/plugins/model/_plugins_admin.class.php on line 1455
Things move VERY slowly in my company. We have one of the most complicated and convoluted release procedures I've ever seen. In order to get even the most trivial 5 minute change into production takes a week minimum. Let's see... Wednesday, a very minor problem was reported in one the systems I manage. Basically the stored procedure was returning a date string in the wrong format. Ok, so I find the stored procedure, and fix it. It takes all of 5 minutes to find and fix the problem. Here are the steps I have to go through to get this in production:

1. Check the file out of Source Safe. Make the minor change and check it in. Make sure to ALWAYS add a comment to the file in Source Safe or any release of this file will get rejected.
2. Write a Bill of Materials in Excel listing all the files that changed, what the change is, where the change is going, what the client impact is, who wrote the change, who tested it.
3. Fill out a QA database change form, listing in detail every change made to the database. This means list every stored procedure, every table, every field of every table, every key, every index, every database that the change has to be applied to.
4. Fill out a Production database change form listing all the same data as the QA database change form.
5. Submit the Bill of Materials, and both DB change forms to the Security Audit team for approval. Wait for a response here...
6. Once the Security team approves it, they forward the info to the QA/CM department who implements in the QA database. QA/CM also creates a PMF (Production Migration Form) at this point.
7. Pass on the changes to your assigned QA resource who goes through and tests the changes in QA. The QA testing approval is then added to the PMF.
8. Once it passes QA testing, the changes are then requested to move to the UAT (User Acceptance Testing)
9. The QA resource then retests the change in the UAT environment and adds their approval for this step to the PMF.
10. Obtain business approval from the project manager and client.
11. Submit a requested implementation date/time. Implementations ONLY go out on Tuesday mornings.
12. All the changes up to this point have to have been completed by Friday at noon. *any* mistakes along the way and the whole process gets rejected and has to be corrected and started again.
13. Assuming all approvals are in by Friday at noon, wait until Monday at noon at which time the PMF either gets approved for implementation or postponed / rejected.
14. If all goes well, you show up Tuesday morning at 6am at the data center and wait while they implement your change. Then you and your QA resource test the changes in production. If there are ANY problems, your change is removed and you have to go back and fix it. Which takes another week...
15. If you fix a bug in Wednesday, you realisticly have 1-2 days to get it fixed, shoved through this convoluted process, and done by Friday at noon in order to get it implemented the following Tuesday!

ARGH! I've had several bugs in my program lately. Total time to fix: 2 days. Total time to get it in production: 2 1/2 weeks and counting!