Planning the Pilot Program

After you test the deployment process in the lab, plan your pilot program. The pilot program is a scaled-down version of the final deployment. The goal of the pilot program is to further test and refine deployment strategies and configurations in everyday use among a limited group of users (for example, between 15 and 50 people).

In this phase, appointed project teams determine the best methods for installing your custom package configurations. Even though you are only testing the installation process, the pilot program sets a precedent for the final deployment; therefore, it is important that all participants are completely prepared. For more information about assembling project teams and selecting your custom package configurations, see Chapter 9 , "Planning the Deployment."

To plan the pilot program, you will need to:

• Select appropriate pilot groups.

• Identify the resources and tasks for the pilot program.

• Create a database to document your progress.

Selecting Pilot Groups

First, you will need to identify your pilot groups and prepare them for the pilot program. If your user groups are large or have very different computing environments or requirements, you may need to select several pilot groups. Select groups that represent the diversity of your computer users. Make sure that the participants have enough time in their schedules and are willing to cooperate in the pilot program. Consider asking for volunteers - you should not ask people to participate who might be too busy meeting deadlines.

Identifying Resources and Tasks

Next, identify the resources and tasks you need to conduct the pilot program. Because the pilot program is your rehearsal for the final deployment, the tasks and resources should be similar to those identified in your deployment plan.

Creating a Database to Document Progress

Before the actual pilot installation begins, create a central database to monitor your progress and document any areas that may require further action. You can use the database to track open items and issues and to measure your actual progress against the original objectives documented in your deployment plan.

.