Webdev/Web Production/Kanban/Mozilla.org: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 3: Line 3:
Last Updated 2013.6.10  
Last Updated 2013.6.10  


<div class="toclimit-3">__TOC__</div>


<h2>Introduction</h2>


<p>
=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]].  
</p>


<p>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.</p>


<h2>Workflow Overview</h2>
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 &amp; 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 &amp; In Progress'''
* Task is pulled into this column when actively being coded/worked on.
** Ready Flag: Pull request filed.


<ol>
    <li><strong>Backlog</strong>
        <ul>
            <li>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.</li>
            <li>Ready Flag: None. Tasks are assumed ready.</li>
        </ul>
    </li>
    <li>
      <strong>Research &amp; Design</strong>
      <ul>
        <li>Tasks that are being started/researched are pulled to this column.</li>
        <li>Ready Flag: Flag applied when ready to be coded, if no R&D needed, still goes into this column and marked ready.</li>
      </ul>
    </li>


    <li>
      <strong>Coding &amp; In Progress</strong>
      <ul>
        <li>Task is pulled into this column when actively being coded/worked on.</li>
        <li>Ready Flag: Pull request filed.</li>
      </ul>
    </li>


    <li>
'''Code Review'''
      <strong>Code Review</strong>
* Task is pulled into this column by whomever is doing the Pull Review.
      <ul>
** Ready Flag: Task is merged (PR+), will be on dev at next automatic push.
        <li>Task is pulled into this column by whomever is doing the Pull Review.</li>
        <li>Ready Flag: Task is merged (PR+), will be on dev at next automatic push.</li>
      </ul>
    </li>


    <li>
      <strong>Testing</strong>
      <ul>
        <li>Task is pulled into this column by whomever is doing the QA, either team members or QA.</li>
        <li>Ready Flag: Passed QA can go live at next push.</li>       
      </ul>
    </li>


    <li>
      <strong>Done</strong>
      <ul>
        <li>Pulled to this column upon deployment and verification in production environment.</li>
        <li>Ready Flag: Not Used</li>
      </ul>
    </li>


  </ol>
'''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.     






<br><br>
'''Done'''
* Pulled to this column upon deployment and verification in production environment.
** Ready Flag: Not Used
Confirmed users
1,052

edits

Navigation menu