Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

14

Work item

(summary)

Description

(details and purpose)

Priority

Tech/non-tech

PBI created

(add number)

Are there dependencies outside TK

Key dependencies

(teams or processes)

Planned completion date

MM-DY-YR

Status details

(latest progress or any notes)

Status (in progress, done)

1

Set-up launch preparation plan in confluence

  • Create a list of items to complete in preparation for MVP launch both technical software related items, release process related and key operational activities.

  • Be very crisp on the priority of the work so that we are planning for completion of anything that will block MVP launch in production.

Important

Non-tech

N/A

-

-

06-04-21

Populating the plan with what is known already.

Status
colourYellow
titleIn progress

2

Vessel registry high level process documentation

  • Documentation of business process flow for current state and future state for MVP iteration.

  • This will help for testing of the end to end flow with workload management, and tweak the process so its as smooth as possible for end users.

Important

Non-tech

N/A

Yes

Registrar supervisors, Change management

06-14-21

First part of new process in draft

Status
colourYellow
titleIn progress

3

Revised registrar work instructions

  • After the new end to end process flow is ready, the detailed registrar instructions will need to be revised to match new process. In scope will be only the instructions that are impacted by MVP rollout and we will minimize change management activities as much as possible (keeping in same repository and current format etc.).

  • This will help rollout training to the impacted daily users of legacy systems and new workload management.

Important

Non-tech

N/A

Yes

Registrars and registrar supervisors

TBD

4

Training of registrars to use workload management

  • Provides an overview of what the new system is and how it works and features that are available

  • This will be in preparation for MVP launch and getting users accustomed to the new tool.

Important

Non-tech

N/A

No?

Registrars and registrar supervisors

TBD

5

MVP rollout strategy and declare target go live date

  • Figure out the segment of service requests that will be used in the system, including launch timelines and percentage of the population.

  • This will be vital part of the MVP rollout plan as it will allow users to be prepared and additional procedural changes that need to be in place depending on the strategy. We can reduce the change management impacts by keeping engagement of non-impacted users to a minimum during the MVP launch.

Important

6

MVP monitoring plan

  • Figure out the key metrics to track process and system stability and how to track the metrics or needed reporting to support.

  • Without key metrics to track it will be challenging to detect issues and problems and to make sure rollout is having the desired impact.

Important

Both

-

Yes

Registrar supervisors, BI team

7

Build MVP operational reporting

Create the reporting infrastructure and dashboards that were in the MVP monitoring plan. Ensure that the reporting requirements are collected from the key stakeholders and they have access to the reporting as necessary.

Important

8

Modifications to vessel registry forms (pending changes)

Non-critical

Non-tech

89

Production release process for MVP

Critical

Both

910

Production release process post-MVP

Important

Both

1011

Issue management process

Important

Both

1112

Runbook (MBM)

Important

Non-tech

Status
colourYellow
titleIn progress

1213

UXR strategy

Important

Non-tech

Status
colourYellow
titleIn progress

1314

Execution of UXR strategy

Important

Non-tech

Status
colourYellow
titleIn progress

15

Review of UXR results and closure of blocking issues

Important

Non-tech

1516

Go no go decision

Important

1617

Communication strategy pre and post launch

Important

1718

User acceptance testing strategy

Important

1819

Execute post production testing plan

Important

1920

Provision and deploy to pre-production environments

Critical

Yes

Cloud team?

Status
colourYellow
titleIn progress

2021

Provision and deploy to production environments

Critical

Yes

Cloud team?

2122

Approvals to launch in production

Critical

Yes

?

22

23

24

25

26

New system of record for to house the procedures from the G drive

  • Training and help documentation is currently in housed in a different repository from workload management. Ideally we can bring the help documentation closer to where the need for it arise, inside vessel registry so its easily accessible during day to day. More thought and options need to be explored for this work.

  • Supports accessibility and easy of updating and keeping documentation fresh and relevant.

High

Both?

-

Yes

Registrars and registrar supervisors

2627