Confirmed users
1,193
edits
MDN/Development/ProcessNext: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "Version: 0.2 <div class="toclimit-3">__TOC__</div> == Purpose == The MDN team plans to adopt Kanban to manage its work. The team feels that Kanban better fits its style of wor...") |
No edit summary |
||
| Line 15: | Line 15: | ||
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. | ||
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. | 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. | ||
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 balance with other priorities) and go through the same phases (to ensure quality). | 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 balance with other priorities) and go through the same phases (to ensure quality). | ||