By Alice Westerfield, Liaison Technologies
In my previous post, I outlined the importance of putting security in place and the questions that need to be asked (and answered) before you get too far down the road. In this post, I’ll address locking down a launch date for your integration project.
Step Four: Finalizing a “Go Live” Date
Obvious, But I’ll Mention It Anyway
It may seem obvious at this point that each member of your team should clearly understand his or her role and responsibilities. They also need to be acutely aware of the date on which the integration solution goes live.
One Missed Call
As you approach the “go live” date, be aware of the possibility of delays. They could be caused by a technical glitch or a bug discovered during the testing process. Or delays may be the result of human error such as an unread email requesting confirmation or a missed voice or text message. These kinds of organic issues could push out your launch date so be as diligent as possible as project manager to keep things on task and on schedule.
Ignition, Sequence, Start!
In your schedule, make deadlines for final details a day or two earlier than the actual launch date. This buffer gives you time to react to last-minute changes or miscalculations. It also provides an opportunity to test the integration processes—and then test them again. And a third, fourth… tenth time, just to be sure.
Next time: Step five – Expect the unexpected