Prototype development service maturity (alpha) assessment

Date adopted: 
November 9, 2018
Last update: 
August 28, 2020

The Government of Yukon uses this to assess the maturity of a service in the prototype development (alpha) stage.

It’s based on our digital service standards and best practices for designing and delivering our online services.

In prototype development (alpha):

  • the service is expected to have been planned to high-quality user standards;
  • compliance is in progress; and
  • the project focus is adapting to ensure a successful service adoption.

This assessment builds on our project intake checklist and the discovery service maturity assessment.

You can download the prototype development (alpha) service maturity assessment template or see what we will assess below.

Executive summary

Summarize the highlights of the assessment. Is the maturity of the service where it is expected at this phase?

Flag any high-risk items that are open. For example, security and privacy.

User needs and user experience (UX)

1. Maintain high standards for user needs

Was the prototype usability tested against the UX artifacts produced in discovery?

What is the plan for triaging usability testing recommendations and incorporating them into the service as improvements?

2. Do ongoing user research

What is the plan to conduct ongoing user research and usability testing with citizens?

3. Make the user experience consistent

Is the service designed to be consistent with the rest of government including the use of standard design patterns, style guide, and common platform components?

Service quality and compliance

Compliance planning was completed in discovery. At the close of prototype development (alpha), measurable progress should have been made on the plan(s) from discovery. These questions measure the service maturity based on this expectation.

4. Safeguard user privacy

If a Privacy Impact Assessment (PIA) is required (as determined in discovery), is it on schedule to be completed as planned?

5. Build a secure service

Is the plan to produce the Security and Threat Risk Assessment (STRA) on schedule?

What is the plan to incorporate STRA improvements or feedback into the final product?

If the service has a payment gateway, is there a plan in place to obtain Payment Card Industry (PCI) compliance?

6. Deliver a bilingual service

When will content be ready for translation by the French Language Services Directorate (FLSD)?

Are there any risks to the service delivery schedule based on translation timing?

7. Make the service accessible

Is WCAG 2.0 AA compliance listed as a deliverable from vendors responsible for building the service?

What is the accessibility testing plan?

8. Change management

Is there a plan in place for change management and code quality?

Use of Agile methodologies

9. Use agile methods

Is the service built using agile user-centered methods? Is there a plan to continuously and frequently iterate on the service?

If a vendor will build all or part of the service, are they aware of agile methodology standards?

10. Use open and common standards

Is the service being built using open standards and common government technology platforms including the eServices platform?

Project ownership and accountability

11. Have a multidisciplinary team

Is there a suitable team still in place that can provide ongoing improvements to and operation of the service? Is this team still led by a senior manager with decision-making authority? What changes have occurred or been identified since previous assessment?

Service adoption planning

At the close of prototype development (alpha), it’s time to plan for service adoption and a successful launch. The questions in the next two sections measure the service maturity based on this expectation.

12. Encourage everyone to use the digital service

Is there a plan in place to move non-digital users to this service?

Is the communication plan in progress from the service owner?

Is training for content and operations staff required?

13. Have a plan for being offline

Is there a business continuity plan in place in the event a service is temporarily offline or unavailable? How will people be affected if the service is offline? What's the plan to get it back online?

Does this service have a lifecycle? For example, not all services are intended to be available at all times. What messaging will be put in place when the service is not active?

14. Collect and report on performance data

What are the performance measures, historic values, and benchmarks to measure the success of the service?

Has the selected tool for collecting and reporting performance data changed since discovery? If yes, why?

15. Test with senior stakeholders

What is the plan to test the service end-to-end with senior stakeholders such as directors or deputy ministers?

Launch planning

Starting to plan service launch while still in prototype development (alpha) increases the chance of a successful launch. This ensures there are no surprises encountered when completing the pre-launch checklist.

16. Post-launch support

Is there a post-launch support plan in progress?

If a vendor is building all or part of the service, are they available for post launch support? Does the client have budget for service sustainment?

17. Test the end-to-end service

Has the service been tested end-to-end in an environment representative of the target system? Was automated and manual testing done? Where will the service be hosted? What is the domain?

If the service will take payments, what is the plan to test the production finance flow?

18. Content updates

Is the content management plan in progress? This details how content updates will be made in the future and by whom.

19. Service ownership

Who will own the service post-launch? This is typically someone not in the eServices team.

20. Senior management approvals

Is a plan in place to get senior management approvals in time for launch?