Post Go-live Support Project Plan
live plan projectThe support provided as part of agreement after go-live is different than the support project itself. Pre Go-Live planning and preparation and post Go-Live adoption and transition to support.
Project Management Document Map Dr Victor Uncategorized Processon Project Management Management Project Charter
But if people are not taking.
Post go-live support project plan. In reality there is usually more knowledge transfer required than actually done during handshake period. Some project managers think that it is the job of the support team to support the software when live and there should not be any phase after project closure. Even before you start with the implementation the Go Live date should be set in mind and the team should start working backwards to end up with realistic targets and dates.
Go-Live Planning Although many activities may remain to complete on the implementation plan before final Go-Live a detailed plan for the actual Go-Live event should be planned and developed at the earliest opportunity. It follows logically that if you dont give adequate forethought to your Go-Live plan you will leave yourself vulnerable to project pitfalls and organizational confusion. This includes training of the existing support function.
Previous Article Previous Next Article Next. As go-live approaches it revisits the support process post go-live. The first key element of Preparation is a system design with the end user in mind.
Clients start using the product after the implementation and deployment are over so we cant afford to breathe a sigh of relief and walk away. Months Prior to Go Live Set your Roll Out Strategy. Although many activities may remain to complete on the implementation plan before final Go-Live a detailed plan for Post Go-Live Support should be planned and developed at the earliest.
Long Term Support or Handling the Known Unknowns This blog will address the first phase Preparation Preparation. However it is part of the service that we provide to the client and deserves equal consideration. Early in the project it explains how post go-live support will be handled.
Go Live Readiness Plan. With the help of David Chou VPCIO Childrens Mercy Hospital Bob Steele HCI Executive VP Clinical Services and Stephen Tokarz HCI Senior VP Training Activation weve compiled a list to help you get started. The whole team is focused on the deployment and go-live activities that the post production support gets little attention.
Apart from making sure the actual Go-Live runs smoothly the ultimate success of your Go-Live depends on two factors. In one of the first meetings with your organization the vendor should explain the project plan including an overview of post go-live support. Most importantly you will want to start by making sure that.
They strongly feels that post production support is not meant for the project team. There are a number of items on your go live readiness plan to consider when determining if you are ready to go live. After the checklist is submitted a Microsoft solution architect will review the project and provide an assessment that describes the potential risks best practices and recommendations for a successful go-live of the project.
Post go-live optimization is a phase that should be included in your ERP project plan and is often overlooked. Receive new career skills every week plus get our latest offers and a free downloadable Personal Development Plan workbook. We must have the same amount.
Immediate Post-Go Live or as we like to think about it Silence is Bliss 3. There may be less support from the management team as post-launch feels more nebulousyou no longer have the clarity of a go live date to point to as a tangible milestone. After the go live the support is provided to remove the bugs from the delivered objects in the production system.
Go live considerations start weeks if not months before the actual go live. Hence there tends to be an overlap which is. Can you lead me to any resources you have on Post Implementation Support.
Contingency date Comments A Key BAU Events A1 Identification Complete Identification of the first time that key business processes are run Developed pack of First Time Useage Report schedule and Tracking Mechanism PIS 030417 No. Your Challenge Create a reality-based management perspective of system support Identify what support teams do Consider your institutional. The ERP project was a short-term assignment Many team members are drafted from your Business offices They are also your best people for system support Why Support is an Issue Money You budgeted for the maintenance agreement Did you plan for the human side.
Sometimes the company may want to get the roll. When the assessment is completed the solution architect will indicate. This is something to make ensure that what has been delivered by the software companies should work perfectly in the production system as per the given requirements.
System design with the end user in mind. Effective Preparation has three core elements. Data reports will be especially helpful for making sure that youre reaching project goals and setting yourself up for success post Go-Live.
This will help you assess the project planning process as well as the actual benefits achieved through the project. An end user. IMPLEMENT A SHARED SUPPORT MODEL The goal is to ensure that a fully qualified issue gets quickly documented routed efficiently to the right resource for triage forwarded to an expert if required to provide a solution the information and status provided back to the user and the issue.
Subscribe to Our Newsletter. This will remind your employees of the approaching change and enable them to ask questions so they can be. This does not.
Monitor Evaluate and Improve Post Go-Live. Building in system health maintenance and operational monitoring plans and then preparing for the next phase. Post Go Live Plan Version 04 Milestone Log Last Updated 09052017 Milestone No Milestone Title RAG Description Acceptance Criteria Owner Planned Date Contingency.
In some cases the solution architect might highlight risk factors and ask for a mitigation plan. For example if you were upgrading from Office 2003 to Office 365 and users did not have a choice but to go along with the upgrade then technically your project was a success. Implement a Shared Support Model.
Your project team will not wait until the go live phase of the project to start thinking about deploying the system. The Ultimate Go Live Checklist ERP Implementation 1. During this phase you should be supporting users in the production environment with training communication and issue resolution via your support team.
Staffing up for user support and issue management. 5 WHITE PAPER Oracle Cloud Applications Post Go Live A ctivities. Many of the Go-Live tasks will take time to prepare for and all activities must be carefully coordinated.
