In the beta phase, we build a working version of the service or website based on the prototypes.
There are a number of steps involved in this phase of development. These steps are:
How long beta takes
Beta could take around 3 to 4 months with a dedicated project team. This will depend on the scope of your project.
Team roles needed for beta
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 Yukon.ca if applicable.
Some teams may also need:
- Business analyst. Responsible for analyzing current business process and aiding the service owner when required.
- Service delivery manager. Responsible for following the standard, leading service maturity assessments and managing project-related contracts.
- Service design manager. Responsible for leading discovery 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 is finished
eServices will run the beta service maturity assessment at this point. Once you have passed the assessment, you can move to the live phase.