Issue link: https://epubs.iltanet.org/i/74024
You've Got To Have Principles as the milestones to get from start to finish. In software implementation projects, that means defining how an application will behave, what new features it will support, and what the new user experience will be compared to the current environment, as described in a "requirements and design" document. Be very specific about the details to ensure there are no surprises or misconceptions that impact the success of the project. Understanding the current environment meant starting with a clear grasp on the firm's call routing at the main office — down to the details of existing phone numbers and call routing across multiple circuits. These were necessary starting points and essential details to ensuring a complete migration with minimal downtime. The end requirement for access fault tolerance and carrier redundancy, and how this would work during a fault scenario, were also necessary elements to document. This ensured that everyone understood the intended finished product and testing plan. • Influential events such as local number portability or DNS changes Define roles and responsibilities. As an extension of the overall project plan, it is critical to understand who does what during the testing process. Having documented responsibilities will help make sure everyone's time is used effectively. Define the testing environment. In order to evaluate the new solution, a properly outlined testing plan must include details of the testing environment. In software implementation projects, this would include a test server(s) and workstation(s). In the world of network migrations, this might mean sourcing additional test hardware if the existing hardware does not support the additional circuits. 3. Build a Testing and Cut-Over Plan A testing plan is the means by which everyone comes to agreement on validating that the new environment has met the requirements of the project. Define the testing process. When managing software implementation projects, this phase is referred to as user acceptance and testing (UAT). In the world of managing network migrations, a testing plan might include: • Carrier testing and acceptance • Installing and connecting the new hardware • Stress testing of the new circuits independent of the existing environment (to identify problems with signaling mismatch, a bad local loop or faulty extended wiring) • Running the necessary testing to verify user access to the new hardware New routers had to be implemented, which made it easier to have a standalone test environment that didn't impact users. On the other hand, we had to test changes to remote clients accessing the network via VPN to account for the public IP address change associated with migrating to a different network provider. Define the cut-over process. If dealing with a telecom hardware migration project, this process entails: • Staging the new hardware • Disconnecting and removing the existing hardware when users are no longer accessing it ILTA White Paper 39