Handover to BAU
Business As Usual (BAU) is exactly what it sounds like – teams completing their everyday work in the usual way. When a project is completed and has been deployed into production, ownership for maintenance and support is typically handed off to the business so that it becomes part of their ongoing operations.
The Handover process to Business as Usual helps ensure the smooth transition of new and enhanced services into the Business As Usual support teams. The support model should be documented and agreed with all of the key people who are going to provide BAU support.'
It is important to organize and implement an orderly and methodical transition from the project team to the team who supports the business day to day, so they are prepared to maintain and support the application without interruption to business as usual.
You need to consider how the business is going to implement future changes, bug fixes, or enhancements after go live.
Prepare a Transition Readiness plan, identifying the key roles and responsibilities for maintenance and provide supporting documentation as necessary. The next step is to get the key stakeholders together and walk them through the process of what it means to be in a Business As Usual state. This review makes clear who is responsible for what. The business owner to the client’s production environments is a critical contact point and needs to be in the loop from a communication perspective so that they can let the business, customers, end users and other interested parties know if and when something goes wrong. Make sure to define all escalation paths so that problems are communicated and resolved as quickly as possible.
The business should always be involved in User Acceptance Testing (UAT) prior to go live so that they are comfortable with the changes being implemented. Similarly, it is important to have a User Acceptance Testing plan in place for any system modifications that might take place post go live.
Published May 8, 2018 — Updated January 11, 2019