@Aklapper the Community Liaison team created a prototype of such a checklist at our team off-site in July. @Rdicerb @Moushira @Quiddity did this make it past the flipchart stage? I don't recall and can't immediately find it on a wiki.

@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.

There is a related topic at the WMF product development discussion page. To avoid duplication, it is better to use that page for discussion, and this task to track progress.

Risker also made some comments about this in https://en.wikipedia.org/wiki/User:Risker/Risker%27s_checklist_for_content-creation_extensions

In T131915#2346445, @Keegan wrote:

• T119891: Document checklist for releasing a new feature - this is complicated, there is no one size fits all checklist, or series of checklists, for releasing a new feature. Each project/product/feature is so very different that treating them with generalities and not nuance is unfair to the end goal. If there is such a possible specific checklist, Risker's one for releasing anything that touches what people use to edit is a good one. That's about as scoped as I would get such a checklist, otherwise it's too restrictive. Risker's checklist is on point because it outlines paths of development that the community will consider harmful.

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.

In T119891#2673420, @Qgil wrote:

For simplicity, I propose to merge this task into T138339: Create a systematic approach to community engagement for product development teams.

+1. (as I'm not sure if Keegan was asked as assignee, or me as task author, or....)