Confirmed users
1,193
edits
MDN/Development/ProcessNext: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Version: 0.2 | Version: 0.2 | ||
<div class="toclimit-3">__TOC__</div> | <div class="toclimit-3">__TOC__</div> | ||
| 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, based on stakeholder feedback, decides which ones the team should complete. 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 four other phases in order: ''Design'', ''Development'', | 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, based on stakeholder feedback, decides which ones the team should complete. 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 four other phases in order: ''Design'', ''Development'', ''Review & QA'', and ''Released''. | ||
The team uses Kanbanery and Bugzilla to manage this process. Each Kanbanery card refers to the Bugzilla bug (created by the ''Mozilla Developer Network Feedback'' form) that describes the original request. The team uses the bug to collaborate as progress is made. For example, the team might use the bug to share | The team uses Kanbanery and Bugzilla to manage this process. Each Kanbanery card refers to the Bugzilla bug (created by the ''Mozilla Developer Network Feedback'' form) that describes the original request. The team uses the bug to collaborate as progress is made. For example, the team might use the bug to share designs or hold technical discussions. | ||
When a phase is completed (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 not skipped when a card is moved. If a phase is not required for a given card, the group responsible for that phase simply marks the card as ''Ready'' immediately after it is pulled in. | When a phase is completed (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 not skipped when a card is moved. If a phase is not required for a given card, the group responsible for that phase simply marks the card as ''Ready'' immediately after it is pulled in. | ||
All requests go through this process. The team can elect to work on any requests that interest them, but they are first approved by the Project Manager (to ensure they | All requests go through this process. The team can elect to work on any requests that interest them, but they are first approved by the Project Manager (to ensure they fit with other priorities) and go through the same phases (to ensure quality). | ||
== Phases == | == Phases == | ||
| Line 27: | Line 27: | ||
=== Design === | === Design === | ||
The team collaborates on a detailed design for the change. The card is marked as ''Ready'' after a designated person (or group) signs off on | The team collaborates on a detailed design for the change. The card is marked as ''Ready'' after a designated person (or group) signs off on a design. | ||
=== Development === | === Development === | ||
| Line 37: | Line 37: | ||
The development team completes a code review and a spot check. Sometimes, additional quality assurance is completed and sign-off is requested from the person (or group) who signed off on the design. The card is marked as ''Ready'' when the team is confident that the change works as designed. | The development team completes a code review and a spot check. Sometimes, additional quality assurance is completed and sign-off is requested from the person (or group) who signed off on the design. The card is marked as ''Ready'' when the team is confident that the change works as designed. | ||
=== | === Released === | ||
The change has been released to the production server. | |||
== Card Management == | == Card Management == | ||
| Line 80: | Line 80: | ||
Every card is assigned to someone in Kanbanery, with the exception of cards in the ''Selected'' phase. Assignment is self-directed. The person assigned to a card is not necessarily the only person working on it, but the person ultimately responsible for ensuring that the card becomes ''Ready''. | Every card is assigned to someone in Kanbanery, with the exception of cards in the ''Selected'' phase. Assignment is self-directed. The person assigned to a card is not necessarily the only person working on it, but the person ultimately responsible for ensuring that the card becomes ''Ready''. | ||
When a person is no longer working on a card, she changes the assignee to ''nobody''. At any point, | When a person is no longer working on a card, she changes the assignee to ''nobody''. At any point, another team member can assign one of these cards to herself and begin working on it. | ||
=== Deadlines === | === Deadlines === | ||