(archive) Node.02 release plan
Launch Readiness
Development
Description | Responsible | Status/Answer | Go/No Go |
---|---|---|---|
Are we Code Complete | Dev Lead | typically Yes or no | |
Are all issues / tasks in the project marked as complete? | Program Lead | typically Yes or No, review issue list and obtain statuses on all items. | |
What is the test program | Dev/Test Lead | Describe the testing program (Create a page as part of this release for the testing program if needed) | |
| Dev Lead | Code needs to be in GitHub and under Continuous Integration. | |
Are there any known issues or limitations with the product? | Dev Lead | If yes, describe where the issues are documented | |
Are any of the issues potential blockers? | Dev Lead | If needed, review the open issues for the version in question. If issues exist, plan to fix or document. Reschedule the launch if needed. | |
How is the release packaged and installed? | Dev Lead | Describe how the release will be delivered to customers, how customers will install the package. (Maybe this needs to be a requirement specified up front.) | |
Have we shown the release to the membership? | Program Lead | Pre-release demo of the release should be given to the membership | |
Have we documented the release?
| Dev Lead/ Program Lead | Describe the technical documentation that will be delivered as part of the release. | |
Link to file issues | Program Manager | How will bugs against the release be tracked. Provide a link to file issues here. Also provide a link to query issues against the release here. |
Customer Facing Teams
Description | Responsible | Status / Answer | Go / No Go |
---|---|---|---|
What is the Marketing Plan | Marketing | Provide a link to the marketing program, and indicate if all items are complete. | |
What is the Support Program | Program Lead | Describe how users will obtain support for the product. How will the support program be staffed, what is the SLA for support. | |
Documentation Program | Program Lead | Describe the external documentation plan. Provide a link if needed. How will the technical documentation be exposed to users. What format will the documentation take. | |
Metrics | Program Lead | Describe how the success of the release will be measured. What are the KPI's - these should map back to the goals of the release. How will the KPI's be collected and published. | |
Licensing | Program Lead | What license is the release licensed under? |