MDN/Development/ProcessNext: Difference between revisions

The MDN team plans to adopt Kanban to manage its work. The team feels that Kanban better fits its style of working and provides benefits that align with current goals.

This document describes and early, minimum viable Kanban process. The team will use and refine this process over time. When the process reaches a certain level of maturity, the team will request feedback more widely and use that feedback to formalize a process that all stakeholders are pleased with.

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.

When the ''Ready criteria'' are met for a phase (see the section [[#Phases|Phases]]), the card is marked as ''Ready'' in Kanbanery. At any point, a team member working in the next phase can pull a ''Ready'' card into his phase and begin working on it. Phases are occasionally skipped. For example, a card that describes a technical change that has no direct impact on design can skip the ''Design'' phase. The group responsible for the phase being skipped should make that determination.