Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Overview

To facilitate the process of design and development for the Vessel Registry project, we are following the UK Government methodology for Agile service delivery laid out in their Service Manual. This process begins with a 4-8 week Discovery phase.

Planned Duration

We have decided to restrict ourselves to 3 Sprints for the Discovery Phase. As there is a considerable amount of existing knowledge for the context, problems, and expected outcomes for this project, it should give us a solid head-start with discovery. We are aiming to finish sooner, however we will go no longer than 3 sprints unless absolutely necessary.

Discovery Goal

The goal of the Discovery phase is to gain a shared understanding of the Vessel Registry service, its users, and their pain points, so that these can be addressed and improved in the solution. We want to reach a common understanding of the expected outcomes so that we can begin working progressively towards that new future-state for the Service.

Goals

  • Establish what the vessel registry service is  

  • Who the vessel registry is for; 

  • Why is the vessel registry important; 

  • What a “good service” looks like  

Outcomes

  • A clear idea of the scope of the new digital service  

  • A shared understanding and buy-in of the senior stakeholders of what we are trying to achieve  

  • What does success look like and a good idea of how to measure success  

  • Think about all the people needed to build an alpha  

Constraints

TBD

Research Plans

Internal Users

Registrars

TBD

Admins

TBD

Data Users

TBD

External Users

Current research proposal

Vessel Owners

TBD

OGDs

TBD

Brokers/Facilitators

TBD

Problems and Outcomes

TBD

  • No labels