Product teams could use guidance on what to include when proposing new projects. Clear communication and information about new projects educations and allows for due diligence on the part of product teams when doing research on an idea.
The outputs for this task will be a set of recommended content that should be included when new products or projects are being proposed by WMF product teams. This will go in the Technical Collaboration Guidelines.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Keegan | T138339 Create a systematic approach to community engagement for product development teams | |||
| Resolved | Qgil | T131915 Technical Collaboration quarterly goals for July - September 2016 | |||
| Resolved | Keegan | T138240 Technical Collaboration Guideline - project information | |||
| Resolved | Keegan | T137826 Recommendations for announcing new project proposals |
First draft set of recommendations: https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Milestone_communication#Proposals
https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Milestone_communication#Proposals cpvers new project proposals, but apparently also new proposals in general (i.e. a new feature in an existing product). I think this is good, but the wording could be clearer (i.e. talking about "proposals" instead of "projects").
When it comes to new project proposals, I think it would be useful to specify a Must-have on documenting the research made user needs, existing alternatives, previous attempts... In software development it is not uncommon to see projects started without a good knowledge of the problem to be solved and what solutions have been tried before.
Other than this, I think this task can be resolved.