All developments need to go through the Digital Information Office (DIO) Change Advisory Board (CAB) before they can be deployed.

About the Change Advisory Board

The CAB consists of members from governance functions within DIO who review and assess changes in the IT environment. 

The framework of CAB includes change preparation and planning, requesting a change, risk assessment, technical/peer review and approval, CAB review and approval, and implementation. This robust process ensures that all changes to an information and communications technology (ICT) environment are documented, reviewed, and planned in a controlled manner to minimise risks that would affect our end users. 

Our deployment process

The steps to deploy to the production environment are as follows:

1. Achieve written client approval

This must state explicitly what is being approved and when it is approved to deploy. An example of written approval is below: 

I can confirm that all the features/issues/items in our release list are now working as expected on the UAT/staging environment and I give my approval to deploy this to Production (the live environment) at HH:MM AM/PM on DD Mmm YYYY.

I am aware that there could be 0–5 minutes outage of the website during the deployment window.

I will communicate to my stakeholders and content editors about this deployment and any content freeze before the deployment date.

[Customer name]

(DE&S will provide guidance on the time and date of the deployment and any content freezes)

2. Submit a CAB request  

The DE&S Platform Principal will prepare a CAB request that includes the client approval, DE&S Director approval and deployment timeline. This must take place on the Friday prior to a CAB meeting.

If written approval is not provided for a CAB request on the Friday prior to the intended CAB meeting, the project will need to go to the following week's CAB meeting and the deployment date will need to be revised.

3. Attend a CAB meeting

CAB meetings occur on Wednesdays from 10:30am–12pm. The DE&S Platform Principal will attend and present the submission on behalf of the project team. At the meeting, the Change Managers will discuss the submission and provide approval or request further information. 

4. Production deployment

Once approved by CAB, the DE&S Platform Principal can deploy to the production environment as per the agreed deployment schedule. This usually takes half a day.

There may be content freezes involved, which means authors of content on that website will not be able to access the CMS during this time. This will be communicated ahead of time as well as at the start and end of the freeze period. 

5. Test in production  

The DE&S producer team will undertake smoke/regression testing on the production environment after deployment. This usually takes half a day.

This ensures that no issues have appeared in deployment, but does not include issues that were present on the test environment. 

6. Inform customers  

Once testing is complete, the producer will inform the client that the website is live in production and communicate next steps. This does not necessarily mean that the website is live to the public.

Once deployed, the customer should test the product to ensure no new issues have appeared since deployment to production. Once verified, written acceptance of the production environment will be sought and the product will enter the warranty phase.