MVP launch preparation plan

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.	Important	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.	Important	Non-tech	N/A	Yes	Registrars and registrar supervisors	TBD
3	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
4	MVP rollout strategy	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
5	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
6	Modifications to vessel registry forms (pending changes)		Non-critical	Non-tech
7	Production release process for MVP		Critical	Both
8	Production release process post-MVP		Important	Both
9	Issue management process		Important	Both
10	Runbook (MBM)		Important	Non-tech
11	UXR strategy		Important	Non-tech
12	Execution of UXR strategy		Important	Non-tech
13	Review of UXR results and closure of blocking issues		Important	Non-tech
14	Go no go decision		Important
15	Communication strategy pre and post launch		Important
16	User acceptance testing strategy		Important
17	Execute post production testing plan		Important
18	Provision and deploy to pre-production environments		Critical			Yes	Cloud team?
19	Provision and deploy to production environments		Critical			Yes	Cloud team?
20	Approvals to launch in production		Critical			Yes	?
21
22
23
24	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
25