Digitial First Design Playbook

To prepare to move to a digital service it is necessary to capture what is known about your current service. We have provided a number of resources to help you to understand the facets of your service and recognize how the service will change when moving to a digital service.

• A business readiness workbook will help you explore if you are ready from a business standpoint.

• A technical readiness workbook will help you understand what systems may be impacted by the change.

• A stakeholder readiness workbook will help you understand how the shift to a new system will affect users and stakeholders of the service.

Completing these workbooks will ensure you understand the facets of your service and prepare you to navigate the changes required to develop the digital service.

Once you have completed the business, technical and stakeholder readiness workbooks you will be prepared to start the application process. It is necessary apply to use the DFD platform since DFD resources will remain limited. Teams that are well prepared and pose the least risk* will be prioritized above projects that are deemed unready or involve higher risk.

To apply:

Complete the DFD intake form available. https:\someURL

Once you have submitted the application the DFD team will review your application to assess your readiness and the risk involved with the project. If accepted as a candidate service for DFD, you will meet with the DFD intake manager and discuss the plans and timelines for your service.

Once your project is accepted you will work with your DSTO partners to design and plan the new service. We have provided a design guide, a backlog guide, a sprint plan template and a rollout plan template, and a change management template for you to use.

What does the design process look like?

Required for design consideration:

• Wireframes or a generalized workflow of what your form(s) will require.

• Accessibility - (will this be fully handled by the accelerated forms?) Being aware of the accessibility requirements for an online service by looking through the DFD accessibility testplan (available here)

• Responsiveness - (will this be fully handled by the accelerated forms?) Do we need to mention it?

At a minimum what is required for planning? (will any of this be required for accelerated forms? - Richard thinks the forms should be built very quickly…)

• Backlog - Epics and features defined.

• Sprint plan - A rough plan of how many sprints, sprint duration,

• Testing plan - How QA will take place and who will perform it

Once your project has been planned and designed you are ready to start development. Your development team will follow the sprint plan laid out during planning. As development progresses you will expand your roll-out plan include pertinent dates for communicating with stakeholders.

Required for development are the follow

• backlog

• sprint plan

• test plan

As your project is nearing completing you will need to assess release readiness and and have a plan for how to manage the rollout through communication with stakeholders regarding the changes for the service.

Required for deployment are the following:

• rollout plan

• readiness assessment

• change management plan