Confirmed users
1,052
edits
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
Last Updated 2013.6.10 | Last Updated 2013.6.10 | ||
=Introduction= | |||
The following describes the flow of tasks through the mozilla.org kanban board. This flow is adapted from the | The following describes the flow of tasks through the mozilla.org kanban board. This flow is adapted from the | ||
[[Webdev/Web_Production/Kanban| general kanban guidelines]]. | [[Webdev/Web_Production/Kanban| general kanban guidelines]]. | ||
Mozilla.org uses the Kanban signal & pull method. Tasks are marked as ready using the green checkmark, this signals that a task is ready for the next stage of work. | |||
==Workflow Overview== | |||
'''Backlog''' | |||
* With some discussion tasks are added to the Backlog and prioritized. Only items that should actually be worked on should be added to this column. | |||
** Ready Flag: None. Tasks are assumed ready. | |||
'''Research & Design''' | |||
* Tasks that are being started/researched are pulled to this column. | |||
** Ready Flag: Flag applied when ready to be coded, if no R&D needed, still goes into this column and marked ready. | |||
'''Coding & In Progress''' | |||
* Task is pulled into this column when actively being coded/worked on. | |||
** Ready Flag: Pull request filed. | |||
'''Code Review''' | |||
* Task is pulled into this column by whomever is doing the Pull Review. | |||
** Ready Flag: Task is merged (PR+), will be on dev at next automatic push. | |||
'''Testing''' | |||
* Task is pulled into this column by whomever is doing the QA, either team members or QA. | |||
** Ready Flag: Passed QA can go live at next push. | |||
'''Done''' | |||
* Pulled to this column upon deployment and verification in production environment. | |||
** Ready Flag: Not Used | |||