Testing and Piloting Windows 2000

Test your Windows 2000 design in a lab before deploying Windows 2000. In the early planning stages, you will need to select testing and piloting sites and assess hardware requirements. As soon as your lab is operational you can use the lab to better understand the product, prove concepts, and validate solutions. Expect the lab to evolve as the project progresses.

In general, provide as much detail as possible in your test plan documents so that your test and deployment teams have all the information they need to be successful. Describe the scope, objectives, methodology, schedule, and resources (hardware, software, personnel, training, and tools) in your test plan. Individual teams and subteams need to create their own test plans for their areas of technical expertise and write test cases. Test cases describe how the testing is to be done. This makes it possible to replicate and compare test results.

In the early phases of the project, testing will focus on components to validate design. Later testing will focus on interoperability of components to ensure that all the pieces work together. You need to test applications for compatibility with Windows 2000. Start by testing features that are mission-critical to your organization and whose design choice would be expensive and time-consuming to change.

Include a plan to escalate any issues that arise to the person most able to resolve the situation. A clear escalation process helps the team focus on the solution and take immediate corrective action.

If you are deploying Active Directory, be sure to provide for application testing with the directory service.

After you verify your Windows 2000 deployment in your lab environment, perform at least one pilot project before beginning your general deployment. The pilot project sets the tone for the final deployment, so it is important to be completely prepared for all aspects of the project. You need to determine the time it takes for installation, the personnel and tools needed to facilitate the process, and the overall schedule. The pilot provides a way to test your deployment plans. The pilot project also provides an opportunity to train your support staff and to gauge user reaction to the product so you can anticipate support needs.

For more information about setting up a test lab, see "Building a Windows 2000 Test Lab " in this book. For more information about pilots, see "Conducting Your Windows 2000 Pilot" in this book.

Note

Complete your pilot project before proceeding to full-scale production deployment. As you complete each phase of your pilot project, document your results, verify that you met your project requirements, and rework your plan if necessary. Resolve any major issues before proceeding to the full-scale deployment phase. Be sure to include all aspects of your production environment in the pilot. For example, if you are going to deploy on an international scale that includes various languages, be sure that you successfully address international language issues in your pilot.