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 4 Next »

Here is a list of activities that will prepare us for the launch of our first production release. This list includes both technical and non-technical activities and some of these activities will be repeated for future releases and some will not necessarily be required.

Priority categories:

1=Critical

2=Important

3=High

4=Non-critical

Priorities defined:

  • Critical work items are considered must have before launch otherwise the launch will not happen.

  • Important work items will not block the launch, but not completing the item may compromise success of the launch, so they need to be completed before launch.

  • High items will not block the launch but they should be completed before launch or as fast followers as they will lead to success of the launch.

  • Non-critical items are nice to have before launch but they can be be done soon after launch as followers.

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

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.

Critical

Non-tech

N/A

Yes

Registrar supervisors, Change management

06-14-21

First part of new process in draft

In Progress

2

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.

Critical

Non-tech

N/A

Yes

Registrars and registrar supervisors

TBD

3

4

5

6

7

8

9

10

11

12

13

14

15

  • No labels