https://phabricator.wikimedia.org/T116676#1834698 and followup comments made me wonder if https://www.mediawiki.org/wiki/WMF_product_development_process should have/document a checklist for releasing a new feature, from early concept to build and release.
@Keegan our notes/docs should all be linked at the bottom of https://office.wikimedia.org/wiki/Community_Engagement_%28Product%29/Mexico/Off-site but I don't think we ever turned the detailed/thorough notes into anything, just a brief slides version so far. I'd love for the comprehensive version (as well as lightweight overview) to be fully produced.
In terms of WMF product development process, I would focus this task on the checklist for a project to enter the Release stage. Projects would reach this point after having gone through Concept, Plan, Design, Build, stages that will have their own checklists which, for practical reasons, I would leave out of this task.
I imagine that checklist containing a small set of points required for any new product or feature (i.e. beta version for testing announced and available for at least X time). Additional points would be optional, or required depending on the impact of the product/feature (i.e. if you are replacing an existing workflow, or if you are changing something in the UX for readers...)
There should also be a definition of low impact changes not requiring this checklist (clear example: a bugfix doesn't require any of this; the patch can be deployed as soon as it has been tested, using the regular process by the Release-Engineering-Team (CCed to this task so they are aware we are discussing it).
It sounds like a good individual or team goal for Community-Relations-Support to be agreed with Product. This checklist will also help answering @Tnegrin's question about how to release small/medium features efficiently.
Now https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Prioritization_list exists and, in general, the Technical-Collaboration-Guidance is the "checklist" requested in this task. For simplicity, I propose to merge this task into T138339: Create a systematic approach to community engagement for product development teams.