English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

3 answers

Address his/her concerns and have a plan to deal with anything that might go wrong.
If he's worried about technical glitches, do extensive testing first, and have contingency plans and a roll-back plan in case something goes wrong.
If he's worried about user acceptance, put someone on PR to pave the way and perhaps organize training for the new system (the roll out could be part of a larger project plan, that addresses these issues).
If he's worried about a shortage of man power for the roll-out, plan everything step by step and make sure you've got all the resources you need.
In short, have him specify his worries, and address them one by one.

2006-09-26 23:02:09 · answer #1 · answered by OMG, I ♥ PONIES!!1 7 · 0 0

First of all you need "real" users testing it (1% to 3% of the total users to make up the testers group).. put it through its pases under the harshest of conditions... we do that on our systems and its worked well. It comes down to not causing production interruptions and assuring managment of its stability once its deployed.

2006-09-26 22:59:10 · answer #2 · answered by Marc 2 · 0 0

You have a back up to get back to in case things go wrong.

You pre-tested it on a closed system, not the real net.

You had rank and file workers test it.

2006-09-26 22:52:09 · answer #3 · answered by Anonymous · 0 0

fedest.com, questions and answers