A boring go-live is a hallmark of a very successful go-live. When your assigned team executes their activities, the steering committee gives the go-ahead for cut over, and at the end of the event, everyone is looking at each other commenting on how “uneventful” it was, success has been achieved. The following are key factors of ensuring a boring go-live.
Understanding the full the scope of the project and establishing the criteria that enables the team to evaluate if they are sufficiently ready is critical throughout all stages of the program. Establishing a formal Go-Live readiness scorecard which covers key requirements across the value stream elements. Elements typically range from assessing Solution Robustness and IT infrastructure readiness to Training Effectiveness and Documentation Update completeness with the key being that all aspects of the operation are accounted for and not just those related to the software or IT. The scorecard needs to include a definition of what it means to be “Ready for Go-Live for each element. Ready typically means that the item has been assessed, measured, proven and tested to the point that the leaders are confident that this value stream element will support operations in the new system. With the plan in place, an organization can begin the process of Go-Live planning.
It all starts with having the right resources involved in the go-live discussions, planning and execution. Large implementations often need a varied skill set to get the job done right the first time. The customer’s IT team will be vital, especially when establishing technical cutover steps, approved methods of data transfer, database and system access, system infrastructure needs, etc. Your implementation partner and internal project team are there to help define successful go-live criteria and overall company readiness for the production system. Finally, the customer’s business team needs to allocate resources to be ready to perform certain go-live validations or data refinements during cutover and just after go-live.
Planning the exact steps to be completed and by what individuals will be key. The Tsunami Tsolutions approach takes and time-boxed, individually assigned, detailed step-by-step process that gets you to the go-live in a know time window. The process accounts for any delays or efficiencies gained during any step, helping companies understand the changes to the expected go-live time. This allows for easy decision making on subsequent actions and the best execution path. It is important to have a designated backup resource (with contact information) assigned to each primary person on each go-live step. Providing all assigned resources updates to when the expected start for their step will occur ensures the right people are available at the time, even in longer go-live events.
The Tsunami Tsolutions project management approach advocates and accounts for the necessary “practice” of the actual go-live event. Once the right people have been identified, and the detailed plan is drafted, it is time for practice. These rehearsals ensure all stakeholders and step owners know exactly what to expect and when. First, it starts with a step-by-step whiteboard walkthrough. Second, data migration dry runs expand on the practice activities. Finally, full go-live rehearsals lead directly into enterprise and user acceptance testing. Each practice run results in a refinement of the planned steps, timings and procedures. Practice also removes confusion and ambiguity from what are typically lengthy and complex go-live process.
Tsunami Tsolutions delivers boring go-lives to our clients with our proven methodologies, advanced tools and exceptional people. To learn more about Tsunami Tsolutions, click here or contact us.
Over decades in aviation, Tsunami Tsolutions has seen airlines, particularly smaller ones with fewer configuration engineers and mechanics, struggle to confidently verify that aircraft are configured with the right allowable parts.
Learn the the vulnerabilities A&D manufacturers face from their own aerospace and defense (ERP) software.
ERP and MRP were designed for repetitive manufacturing. How are IFS and Tsunami Tsolutions delivering shipbuilding ERP?
New partnership leverages expertise of both companies to field FireSwarm’s integrated response platform
A boring go-live is a hallmark of a very successful go-live. When your assigned team executes their activities, the steering committee gives the go-ahead for cut over, and at the end of the event, everyone is looking at each other commenting on how “uneventful” it was, success has been achieved. The following are key factors of ensuring a boring go-live.
Understanding the full the scope of the project and establishing the criteria that enables the team to evaluate if they are sufficiently ready is critical throughout all stages of the program. Establishing a formal Go-Live readiness scorecard which covers key requirements across the value stream elements. Elements typically range from assessing Solution Robustness and IT infrastructure readiness to Training Effectiveness and Documentation Update completeness with the key being that all aspects of the operation are accounted for and not just those related to the software or IT. The scorecard needs to include a definition of what it means to be “Ready for Go-Live for each element. Ready typically means that the item has been assessed, measured, proven and tested to the point that the leaders are confident that this value stream element will support operations in the new system. With the plan in place, an organization can begin the process of Go-Live planning.
It all starts with having the right resources involved in the go-live discussions, planning and execution. Large implementations often need a varied skill set to get the job done right the first time. The customer’s IT team will be vital, especially when establishing technical cutover steps, approved methods of data transfer, database and system access, system infrastructure needs, etc. Your implementation partner and internal project team are there to help define successful go-live criteria and overall company readiness for the production system. Finally, the customer’s business team needs to allocate resources to be ready to perform certain go-live validations or data refinements during cutover and just after go-live.
Planning the exact steps to be completed and by what individuals will be key. The Tsunami Tsolutions approach takes and time-boxed, individually assigned, detailed step-by-step process that gets you to the go-live in a know time window. The process accounts for any delays or efficiencies gained during any step, helping companies understand the changes to the expected go-live time. This allows for easy decision making on subsequent actions and the best execution path. It is important to have a designated backup resource (with contact information) assigned to each primary person on each go-live step. Providing all assigned resources updates to when the expected start for their step will occur ensures the right people are available at the time, even in longer go-live events.
The Tsunami Tsolutions project management approach advocates and accounts for the necessary “practice” of the actual go-live event. Once the right people have been identified, and the detailed plan is drafted, it is time for practice. These rehearsals ensure all stakeholders and step owners know exactly what to expect and when. First, it starts with a step-by-step whiteboard walkthrough. Second, data migration dry runs expand on the practice activities. Finally, full go-live rehearsals lead directly into enterprise and user acceptance testing. Each practice run results in a refinement of the planned steps, timings and procedures. Practice also removes confusion and ambiguity from what are typically lengthy and complex go-live process.
Tsunami Tsolutions delivers boring go-lives to our clients with our proven methodologies, advanced tools and exceptional people. To learn more about Tsunami Tsolutions, click here or contact us.
Over decades in aviation, Tsunami Tsolutions has seen airlines, particularly smaller ones with fewer configuration engineers and mechanics, struggle to confidently verify that aircraft are configured with the right allowable parts.
Learn the the vulnerabilities A&D manufacturers face from their own aerospace and defense (ERP) software.
ERP and MRP were designed for repetitive manufacturing. How are IFS and Tsunami Tsolutions delivering shipbuilding ERP?
New partnership leverages expertise of both companies to field FireSwarm’s integrated response platform
Phone: +1.860.266.6885
© 2021 TSUNAMI TSOLUTIONS
Phone: +1.860.266.6885
© 2021 TSUNAMI TSOLUTIONS