Engagement/Developer Engagement/Process Documents: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "= Prioritization = {{admon/note|Submitting a feature or project request|To propose a feature or project, '''[https://docs.google.com/a/mozilla.com/forms/d/1UbMOwZh7kgIB0W659T...")
 
(replace with redirect)
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Prioritization =
#REDIRECT [[MDN/Product_roadmap#Process]]
 
{{admon/note|Submitting a feature or project request|To propose a feature or project, '''[https://docs.google.com/a/mozilla.com/forms/d/1UbMOwZh7kgIB0W659Tn9Vq3mS4Nc0XrM9J3aisRa17Y/viewform complete the (prototype) intake form]'''. }}
 
== Overview ==
 
Developer Relations includes a wide variety of activities and efforts designed to develop and maintain connections between Mozilla and a global community of web developers. There are numerous stakeholders in the effort and many great ideas to choose from. This process describes how we select what to work on next.
 
== Improving the process ==
 
This process includes regular reviews to ensure it continues to be effective. Feedback is welcome: email engagement-developers@lists.mozilla.org or join  one of [Engagement/Developer_Engagement#Meetings our regular meetings].
 
== Timeline ==
 
Prioritization of large projects happens on a quarterly cycle. Proposals are welcome any time. Reprioritization midway through a cycle is unusual, but not impossible.
 
=== At any time ===
* Anyone can [https://docs.google.com/a/mozilla.com/forms/d/1UbMOwZh7kgIB0W659Tn9Vq3mS4Nc0XrM9J3aisRa17Y/viewform submit a new project proposal for review].
* Product leads will steer large requests toward the intake form.
* The product manager can convene a meeting of product leads to adjust current priorities immediately in response to new information or conditions
 
=== In the last month of a quarter ===
* The product manager will convene Product Leads to review the process and adjust
* The product manager will solicit Stakeholder feedback on a curated list of projects proposed via the intake form
** Specifically, the product manager will ask Stakeholders to nominate projects for immediate prioritization, and will work with Stakeholders to understand their nominations
* The product manager will prioritize projects and convene a meeting of Product Leads to review and commit
 
=== Throughout the quarter ===
* Product Leads will work with their teams to deliver projects and features
* Product Leads and the product manager will work to articulate upcoming projects and features so they are ready for implementation
 
== Stakeholders ==
 
This process depends on a handful of Product Leads and on a larger list of representatives from various stakeholder groups.
 
'''Product Leads:'''
 
* Mark Coggins (Evangelism)
* Luke Crouch (Engineering)
* Ali Spivak (Content and Community)
 
'''Stakeholders:'''
 
* Developer Relations Engineering
* Developer Relations Content
* Developer Evangelism
* Developer Relations Community
* Developer Tools
* Developer Frameworks
* Web Compatibility
* Addons
* Product Marketing
 
'''Product Manager:''' Justin Crawford
 
== Links ==
 
[https://docs.google.com/a/mozilla.com/forms/d/1UbMOwZh7kgIB0W659Tn9Vq3mS4Nc0XrM9J3aisRa17Y/viewform Submit a new project proposal]

Latest revision as of 17:47, 19 December 2014

Redirect to:

Retrieved from "https://wiki.mozilla.org/index.php?title=Engagement/Developer_Engagement/Process_Documents&oldid=1043139"