Core goal: Organized community engagement across all stages of a common product development process
We will keep working on a common product development process documented, registering constructive and productive community engagement in all stages. All WMF Product teams will be encouraged to follow this process and interact with the communities under the terms agreed. Communities will be able to effectively contribute to and influence the planning and prioritization of new features, as well as negotiate how and when these features are deployed to their wikis. We will continue progressing on this goal through continuous improvements agreed with our communities and dev teams.
Project/Initiative 1: Consolidation of a participative product development process
Refine and document systematic approaches for community engagement across the different stages of product development. Involve the communities in the design and the improvement of this process. Inform the communities how to follow and participate in WMF Product projects.
Project/Initiative 2: Community liaison support to WMF Product teams
Direct support provided to WMF Product teams around new initiatives and ongoing complex projects (e.g. VisualEditor, Community Wishlist). Our support focuses on connecting our communities and development teams through their excitement and concerns, helping them to work with each other. We help providing institutional memory, reaching out to volunteers, finding common interests, anticipating potential problems, and recommending ways forward. Discovery, Reading, Editing, and Community Tech will have a community liaison permanently appointed. More liaisons will be available for specific project collaborations.
Milestones/Results/Impact
Please provide milestones/results/impact and describe how they will impact/contribute to the Wikimedia movement and projects and/or the Wikimedia Foundation.
Project/Initiative 1:
Coming soon, we want to hear feedback about the goals & projects first.
Project/Initiative 2:
Coming soon, we want to hear feedback about the goals & projects first.
Key Performance Indicators (KPIs) or Metrics to measure milestones/success of projects/initiatives
Please ensure that these are both qualitative and quantitative. Some departments may have the same metrics as the following 7 Global Metrics identified for the FDC proposals. Others may need to identify their own KPIs or metrics that are appropriate for their objectives. For example a supporting function such as Office Admin, KPIs or metrics may be in the form of Service Level Agreements.
Global Metrics
- Number of active editors involved
- Number of new registered users
- Number of individuals involved
- Number of new images/media added to Wikimedia article pages
- Number of articles added or improved on Wikimedia projects
- Number of bytes added to and/or deleted from Wikimedia projects
- Learning question: Did your work increase the motivation of contributors, and how do you know?
Project/Initiative 1:
Number of non-WMF participants involved in every stage of the product development process
Number of new registered individuals participating in the product development process
Percentage of active WMF software projects following the product development process
Number of community-driven software projects following the product development process
Number of community conflicts disrupting or delaying product release plans
Satisfaction survey for participants in the process and power editors
Project/Initiative 2:
Coming soon -- see T124155: Review key performance indicators (KPIs) for Community Liaison and Developer Relations
See also T124420: Technical Collaboration narratives and budget for strategic work
Previous description
The first deadline of the WMF Annual Plan (T124019) is
Wednesday, February 3 - Initial budgets and narratives are due for Core Work
Core work budgets for 2016-17 to include: staffing, travel, consultants, equipment, off sites, etc. needed to support current work and projects and to continue those projects for the coming fiscal year, as appropriate, are completed and sent to Finance.
February 3 for all WMF means we need to have a solid draft by Jan 28, and this means that we need to start the work right now.
While a lot of this work is counting beans looking at this fiscal year's budget, the distinction between core and strategic poses an interesting question: how much time are CL and DevRel putting in core work? For a definition of core, see Tracking core and strategic work.
(snip)