Previous | Next

Conducting the Pilot Rollout

In conducting the pilot rollout, you simulate the final installation process, test the capabilities and performance of the system, survey user feedback, and make adjustments as needed. Repeat this process for 32-bit applications.

Simulating the Installation Process

The schedule for the pilot rollout should simulate — on a smaller scale — the schedule of the final rollout. As you conduct the pilot rollout, you may find that certain tasks take more or less time than expected, that some tasks need to be added, or that some tasks can be left out. Modify the pilot rollout schedule to account for such changes, and use the pilot schedule for projecting the final rollout timetable.

Testing Windows 98 Performance and Capabilities

In addition to the technicians responsible for conducting the pilot installation, extra technicians should be assigned to measure, observe, and test the installation. By tracking the time per installation, handling problems that arise, and identifying areas for improvement or automation, these individuals help ensure the success of both the pilot and final rollouts by making the installation more efficient.

In addition, after Windows 98 has been installed, these technicians test system capabilities, such as remote administration, for proper operation and monitor the client computers for performance, stability, and functionality, highlighting any inconsistencies with the lab configuration.

Surveying Users for Feedback

The final part of the pilot rollout involves surveying the users to gauge their satisfaction and proficiency with the new installation and to evaluate the level of training and support provided. Test users’ proficiency by having them perform a few common tasks or use several of the new features in Windows 98 for; example, have them register their survey results on the server.

When the survey results have been collected, combine them with the ideas for improvements identified during the pilot rollout. Use this information to prepare a checklist of open issues that must be resolved prior to the final rollout. Then assign team members to take the actions necessary to solve problems or make improvements. Indicate on the checklist how and when each item was resolved, adjusting the deployment plan if appropriate.