A Customer RACI matrix should be completed within each team to confirm who should approve and who should be informed of a release into UAT and into Live. See example RACI at the end of this document. This may need to be reviewed per release for any changes that need to be made to the RACI for the specific release.
Identify Release Type (Major or Minor)
Major Point releases any project over 1 month of effort should be considered Major, small bug fixes, minor point (weekly) iterations or emergency changes should follow the Minor Release type.
ADL and Consultant complete a risk assessment of the change and mitigation of risk and add this into the Halo Release Note.
Release note created with proposed dates (separate Release Notes for UAT and live) for approval internally and by the Client via Halo.
Any specifics around the Hypercare period or process
Approval of a change in Halo means that the person has:
Confirmed that the date and time specified is acceptable.
Confirmed that they have reviewed and agreed to the change in Halo.
Confirmed that they understand any potential impact the change may have on their work or the work of others.
Confirmed that they have taken any necessary steps to prepare for the change.
Major: ADL, Consultant and Test Analyst complete an assessment of areas of change and advise on any areas they consider essential for Client targeted testing and add these to the release Note in Halo.
Major: Client assesses the advice received and the release note and adds in any further tests felt to be necessary to Halo
The ADL uploads the backout plan into Halo.
The ADL and Consultant document any post-release activities in Halo.
Major: For Live, the Client provides a plan for the code release, including all prerequisite and post-release business tasks as well as the technical tasks documented on the Release Note. This should be walked through with all interested parties (including other 3rd parties) with everyone confirming the activities they are responsible for. Once agreed, this should be uploaded into Halo.
Major: Before approving, a meeting should be scheduled with all approvers and affected parties (including other 3rd parties) to review/agree:
Minor: Before approving, a meeting should be scheduled with all approvers
On completion of the meeting the release note is issued to the following via Halo :
for approval to: Xiatech: ADL, Consultant, Tester Client: Change/Release Manager, Client Product Owner (and anyone nominated by the client).
for notification to 2 email groups: Xiatech: via an email distribution group that includes Service Desk, COO, CTO, Scrum Team and any other interested parties. Client: via a client email distribution group that includes Change Manager, Client Service Desk and any other interested parties.
In addition, approval of a change in Halo implies a commitment to support the change and to ensure its successful implementation. This may involve communicating the change to others, updating documentation or procedures, and providing any necessary training or support to colleagues.
Wondershare EdrawMind
