This phase consists of simulating the final installation process, testing the capabilities and performance of the system, surveying user feedback, and making adjustments as needed.
The schedule for the pilot rollout should simulate¾on a smaller scale¾the schedule for the final rollout. As you conduct the pilot rollout, you might 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.
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 MSMQ and your MSMQ-based application are installed, these technicians test system capabilities for proper operation and monitor the dependent client and independent client computers for performance, stability, and functionality, highlighting any inconsistencies with the lab configuration.
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 supported by your MSMQ-based application.
When collected, combine the survey results with the ideas for improvements identified during the pilot rollout. Use this information to prepare a checklist of open issues that must be resolved before the final rollout. Then assign team members to take the actions necessary for solving problems or making improvements. Indicate on the checklist how and when each item was resolved, adjusting the deployment plan if appropriate.