MDN/Development/ProcessNext: Difference between revisions

MDN/Development/ProcessNext (view source)

Revision as of 18:23, 6 March 2013

319 bytes removed , 6 March 2013

→‎Card Management

John Karahalis

Confirmed users

1,193

edits

@@ Line 42: / Line 42: @@
 == Card Management ==
+=== Work in Progress Limits ===
+The team uses Work in Progress (WIP) limits to control the amount of work being done at any one time. A card is not pulled into a new phase if this limit has already been reached.
+* Selected: 3
+* Design: 3
+* Development: 5
+* Review: 3
 === Work Types ===
@@ Line 53: / Line 62: @@
 === Size ===
-Everything on the Kanban board should be roughly equal in size. This makes work less intimidating and easier to handle. John works with the team to find large high-priority items in the MDN product backlog and break them down to be roughly equal in size.
+Cards are roughly equal in size. If a request seems particularly big, the MDN Project Manager works with the team to break it down.
 === Assignment ===
-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 the ''Ready criteria'' are met.
+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 the card becomes ''Ready''.
-If a person is no longer working on a card, he should change the assignee to "nobody". Anyone else who comes along should feel free to pick up "nobody" tasks and work on them themselves.
+When a person no longer wishes to work on a card, he changes the assignee to ''nobody''. Any other team member can assign a ''nobody'' card to himself and begin working on it.
 === Deadlines ===
@@ Line 67: / Line 76: @@
 === Subtasks ===
-Team members are encouraged, but not required, to use the ''Subtask'' feature of Kanbanery to break their work into more manageable pieces. Subtasks are only used to track work in the current phase.
+The team is encouraged, but not required, to use the ''Subtask'' feature of Kanbanery to break work into more manageable pieces.
 === Blockers ===
-If a card cannot move to the next phase until some work is done, that work is marked as a ''Blocker'' in Kanbanery. The Blocker might be another card, the address of a WebOps bug or just a written description of the impediment.
+If a card cannot move forward until some other work is done, that other work is marked as a ''Blocker'' in Kanbanery. The blocker might be another card, the address of a Bugzilla bug, or even just a written description of the impediment.
-=== Work in Progress Limits ===
-Important to note that these describe active work being done. Columns are not queues. If only 3 cards can be actively worked on in a column, the WIP limit should be 3, or 4 to allow for some flexibility. There should not be a backlog of things going on in a column -- just things being actively done.
-* Selected: 3
-* Design: 3
-* Development: 5
-* Review: 3
 == Planning and Retrospective meeting ==