Confirmed users
1,193
edits
MDN/Development/ProcessNext: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
=== Review & QA === | === Review & QA === | ||
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 team considers not only functionality but also security, performance, and other important factors during this phase. The card is marked as ''Ready'' when the team is confident that the change works as designed and meets other quality standards. | 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 detailed design. The team considers not only functionality but also security, performance, and other important factors during this phase. The card is marked as ''Ready'' when the team is confident that the change works as designed and meets other quality standards. | ||
=== Released === | === Released === | ||
A card is moved here when the corresponding change is pushed to the production server. | |||
== Card Management == | == Card Management == | ||
| Line 41: | Line 41: | ||
=== Work in Progress Limits === | === Work in Progress Limits === | ||
The team uses Work in Progress (WIP) limits to | The team uses Work in Progress (WIP) limits to limit the amount of work being done at a given time. A card is not pulled into a new phase if this limit has already been reached. | ||
{| class="wikitable" style="background-color: transparent" | {| class="wikitable" style="background-color: transparent" | ||
| Line 70: | Line 70: | ||
=== Size === | === Size === | ||
Cards are roughly equal in size. If a request seems particularly big, the MDN | Cards are roughly equal in size. If a request seems particularly big, the MDN project manager works with the team to identify a smaller piece to start on. A card is created for that piece and added to the ''Selected'' column. The process is then repeated until the entire request is completed. | ||
=== Assignment === | === Assignment === | ||
| Line 78: | Line 76: | ||
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, | When a person is no longer working on a card, he changes the assignee to ''nobody''. At any point, another team member can assign one of these cards to himself and begin working on it. | ||
=== Deadlines === | === Deadlines === | ||
The ''Deadline'' feature of Kanbanery is used to highlight changes that have hard deadlines. The team and | The ''Deadline'' feature of Kanbanery is used to highlight changes that have hard deadlines. The team and project manager pay special attention to these cards to ensure they are completed on time. | ||
=== Subtasks === | === Subtasks === | ||
The team is | The team is encouraged to use the ''Subtask'' feature of Kanbanery to break work into more manageable pieces. | ||
=== Blockers === | === Blockers === | ||
| Line 100: | Line 98: | ||
== Planning and Retrospective Meeting == | == Planning and Retrospective Meeting == | ||
The development team, | The development team, product manager, project manager and interested users meet every two weeks to discuss process improvements and review the state of development. | ||
== Working with contributors == | == Working with contributors == | ||