Aside from the technical specifics, what should be on your checklist for when you go live with a program? Are there last minute things you can do to make a piece of software go into production smoothly? (assuming you used sound principles in development and tested the average amount) More testing? Discussion with the client? Last minute optimizations?
Make sure today isn't Friday.
Never push code into production on a Friday. :)
There's no going live day. There is a going live process. Depending on the kind of software, you could deploy to selected beta testers first (Google-style), and expand the user base.
The same applies if the software is replacing manual processes.
If the software is replacing another system, it is harder, and you should should plan for simultaneous operation of both systems, until there is enough confidence in that the old system can be turned off.
At any rate, you should expect problems, so it is best to have a thorough risk assessment with ready-to-go mitigation and contingency strategies. The risk of an all-or-nothing launch plan is too high.
|show 11 more comments|
I think that's a fairly generic question, so of course I'm going to have to reply with a generic answer. My opinion is that it's safe to assume that there will most definitely be problems with your software, so what you should plan for on "Going Live Day" aside from making it available for download is this.
Be ready to correct critical errors within the first couple weeks of going live with someone dedicated to the task. When the critical errors are fixed, you can begin to handle the major errors. :)
As other answerers have noted, it's so high-level a question it's hard to answer very specifically. I will just say this: it's long-standing web developer's superstition that a web site launched on a Friday will never get an audience or produce any ROI. A friday afternoon launch is especially the kiss of death.
At this point, I'm happy to say 100% of my clients have bought into this superstition.
There are no last-minute things. There can't be.
First you get it to work, securely, quickly, and reliably.
Once it's working, you introduce it to users. Perhaps as a pilot or alpha-test.
Then, after you make needed enhancements, you introduce more users. Perhaps as a beta-test.
Then, after you make needed enhancements, you introduce more users.
There's no moment at which you "go live".
You progressively introduce more users.