https://www.mediawiki.org/wiki/WMF_product_development_process offers an overview of the WMF product development process. It should be a self-explanatory page, providing links to subpages where the details about stages and audiences can be found.
|Duplicate||None||T116294 A guide for WMF Engineering teams to prevent known problems with volunteers|
|Unknown Object (Task)|
|Open||None||T125805 WMF product development process 1.0|
|Open||None||T125806 Consolidate the WMF product development process overview|
Posting here the comments moved from the WMF product development process content page:
- Why are terms like "Community members" capitalised and sometimes written "Community Members" even? Is the uppercase referring to some special definition of the term for the purpose of this document (I don't see one)? I'd be interested in understanding why the "Understand" part doesn't mention end users, maybe they are included in a special definition of "Community member" but we don't know. [[User:Nemo_bis|Nemo]] 07:40, 29 January 2016 (UTC)
- The "generally are" and "are generally driven" sentences are unclear, for instance how can you Plan and Release without coordinating with the end users/target wikis and how can Develop not consider volunteer developers and developers of other areas? Worse than that, the phases are of little use if you don't describe how to (not) proceed from one to the next. The most common need is to halt an idea at the "Understand" phase, avoiding that it ever reaches the "Concept" or "Plan" phase. How do we kill bad ideas on time? [[User:Nemo_bis|Nemo]] 07:51, 29 January 2016 (UTC)