POC-to-Production Go/No-Go Analysis
POC-to-Production Go/No-Go Analysis[edit]
- Control
The Product Team should work cross-functionally with relevant Stakeholders to define and document a Go/No-Go checklist that considers qualitative and quantitative factors in the following areas: (a) Can POC-to-Production Checklist be adequately addressed; (b) Is the Product Cost Analysis still feasible; (c) Does the Product Team have approval for a Product maintenance budget; (d) Are the updates, upgrades, and add-ons to the data infrastructure near completion; (e) What is the state of customer process reconstruction and end-user training; (f) Has the failsafe, rollback, or emergency shutdown plan been completed and approved; and/or (g) Have the communication and mitigation plans in case of failsafe, rollback, or emergency shutdown been completed and approved.
- Aim
To (a) ensure that the solution should be deployed in production and/or Product Domains; and (b) highlight associated risks that might occur in the Product Lifecycle.