Creating a Pilot Plan
Updated: March 28, 2003
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
During the planning phase of the deployment project, product management, program management, and release management teams collaborate to create the pilot plan. The pilot plan defines the scope and objectives of the pilot and identifies pilot participants and where the pilot will be conducted. It includes a schedule for deploying and conducting the pilot and plans for training and communicating with pilot participants, evaluating the pilot, identifying risks and contingencies, and other key activities that occur during a pilot deployment.
You have various options for how to conduct your pilot. For example, you might have multiple pilots, with a separate pilot for Windows XP Professional and one for Windows Server 2003, or you might introduce your implementation progressively with a staggered rollout, gradually adding more user groups to your pilot.
If you plan to conduct multiple pilots, develop a pilot plan for each. For example, if the subteam responsible for deploying a particular operating system plans to conduct its own pilot, that subteam should write a pilot plan. Even if you do not plan to conduct multiple pilots, each subteam can contribute to the overall pilot plan.
Figure 4.3 illustrates where creating a pilot plan occurs in the deployment pilot process.
Figure 4.3 Creating a Pilot Plan
When the pilot plan is ready for review, have project team members, necessary support personnel, and management representatives read and approve the plan. Be sure that the supervisors of everyone directly affected by the pilot have a chance to review the plan. For example, if the schedule allots time for a particular user group to participate in the pilot, have the supervisor of that group review the schedule.