2.4. Testing and PilotingThe implementation of MOM 2005 at Leaky Faucet is a significant event that will touch every server. To reduce the risk of something going wrong during the implementation, the MOM administrators have gathered the business and technical requirements, planned out their design, estimated how much data will be collected per day, planned out database sizes, and prepared the environment for inter-component communication. The next step is to test MOM 2005 and figure out what changes are needed. This is very hard to do until there is something to work with. The director of IT requires that the following tasks be completed before the production rollout is authorized:
The Windows team creates a test environment that mirrors the production environment on critical points of configuration, but not scale. It consists of a single management server, a SQL Server that will house both the operations database and the reporting database and web site, and one of each type of server to be managed. All of the consoles will be installed on the management server as well as on desktops. The remote site support administrators will help test the overall security and Web console functionality. Next, the test plan is reviewed to make sure the deliverables are covered. This plan starts after MOM 2005 has been successfully installed and configured. During piloting, the following must be accomplished:
Leaky Faucet sets a start and end date for the pilot to avoid scope creep and prevent the pilot from rolling straight into the production implementation . The pilot duration is estimated to take 21 days (training aside). At the end of this time, Leaky Faucet will take all of the feedback from the key stakeholders, as well as all that they learned, and modify the design if necessary. The rollout plan will be finalized in documented form. This primary deliverable from the pilot will help reassure everyone. |