Beta testing and live

Date adopted: 
August 17, 2020
Last update: 
August 18, 2022

As we work through Beta testing and live, we build a working version of the service or website based on the prototypes we developed earlier in Prototype development (Alpha).

How long Beta testing and live takes

Beta testing and live could take around 3 to 4 months with a dedicated project team. This will depend on the scope of your project.

3 steps to work through in Beta testing and live

  1. Develop a Beta
  2. Private Beta
  3. Public Beta

Team roles needed for Beta testing and live

Your project team should be consistent through all design and delivery phases. This ensures the successful delivery of your service or website.

Department that owns the service or website

  • Service owner. Responsible for ongoing delivery of the service or website by their department. Will have strategic decision-making authority.
  • Subject matter experts (SMEs) from the department. Familiar with the delivery of the existing service or website.
  • Project manager. Responsible for managing the project schedule, scope, and budget.
  • Communications analyst. Responsible for coordinating and producing supporting content for the service or website. This includes the related page on if applicable.

Some teams may also need:

  • Business analyst. Responsible for analyzing current business process and aiding the service owner when required.


  • eServices delivery manager. Responsible for following the standard, guiding the project through the government's service delivery process, coordinating service maturity assessments and managing project-related contracts.
  • User experience manager/Service design manager. Conducting the service maturity assessments and ensuring what gets designed is aligned with the overall eServices strategy and user experience.
  • Web architect. Responsible for the technical architecture and implementation of the service.

How you know when Beta testing and live is finished

Your eServices delivery manager will ensure you have completed the objectives for developing the beta (private and public) and you've taken the steps to ensure the service will be adopted by users.

Once this is done, they will coordinate the required Beta service maturity assessment with an eServices user experience manager. The user experience manager will complete the assessment and send you a report that outlines work required to be completed so your service can go live.


Go back to: Prototype development (Alpha)
Next step: Develop a Beta