MDN/Development/ProcessNext: Difference between revisions

no edit summary
No edit summary
Line 11: Line 11:
== Overview ==
== Overview ==


Users and other stakeholders can request changes to the MDN at any time using the [https://bugzilla.mozilla.org/form.mdn Mozilla Developer Network Feedback] form. The MDN Project Manager occasionally reviews these requests and decides which ones the team should complete based user and stakeholder feedback. For each of these, a new Kanban card is created and added to a phase called ''Selected''. Over time, these cards move out of ''Selected'' and through five other phases in order: ''Design'', ''Technical research'', ''Development'', ''Review & QA'' and ''Archive''.
Users and other stakeholders can request changes to the MDN at any time using the [https://bugzilla.mozilla.org/form.mdn Mozilla Developer Network Feedback] form. The MDN Project Manager occasionally reviews these requests and decides which ones the team should complete based user and stakeholder feedback. For each of these, a new Kanban card is created and added to a phase called ''Selected''. Over time, these cards move out of ''Selected'' and through five other phases in order: ''Design'', ''Development'', ''Review & QA'' and ''Archive''.


The team uses Kanbanery and Bugzilla to manage this process. Each Kanbanery card references the Bugzilla bug (created by the ''Mozilla Developer Network Feedback'' form) that describes the original request. During development, the bug is used to collaborate and share progress. For example, the team might use the bug to share mock-ups or hold technical discussions.
The team uses Kanbanery and Bugzilla to manage this process. Each Kanbanery card references the Bugzilla bug (created by the ''Mozilla Developer Network Feedback'' form) that describes the original request. During development, the bug is used to collaborate and share progress. For example, the team might use the bug to share mock-ups or hold technical discussions.
Line 42: Line 42:
* A written description of behavior has been shared
* A written description of behavior has been shared
* A designated person (or group of people) has signed off on these assets
* A designated person (or group of people) has signed off on these assets
=== Technical research ===
==== Activity ====
The team researches technical solutions to implementing the change.
==== Ready criteria ====
* The team has determined how the change will be implemented. A written record of this can be helpful, but is not always necessary.


=== Development ===
=== Development ===
Confirmed users
1,193

edits