Kanban board
- Noreen Dertinger
Overview
The Kanban board contains our daily tasks.
Current Kanban board
Below is a table with the current columns, their current descriptions and updates to those definitions that I am proposing.
A key change in these definitions is that “in progress” is updated to reflect is that development testing should occur while the work is in progress before it is moved to the “committed” column.
I am noticing a number of repetitive requests/issues and looking for a way for those to be reflected to make it easier to fix recurring issues faster.
A point of feedback, from our discussion today, is that we may have too many columns. May be possible to handle some items via states.
As far as the “blocked” column, I am proposing managing it via a blocked state and if possible, tracking it in the to-do column (person who blocked the item should retain ownership and track it to a resolution).
As far as naming of, and content of the Kanban board, my understanding is that this can be customized by project team, as far as column names, layout, etc. In some of the layouts I’ve seen it may be possible more easily track repetitive tasks. Here is a link to some samples:
https://kanbanize.com/kanban-resources/kanban-software/kanban-board-examples#software_dev_team_kanban_board_examples )
Column | Original | Proposed. |
Backlog (New) | Need to be reviewed/prioritized by PO and Scrum master | Need to be reviewed/prioritized by PO and Scrum master
Has acceptance criteria that have been agreed to by the PO and requester
Is it ready to be actioned by the team? (We should to agree on a definition of ready) |
To Do (Approved) | Tickets in this column are ready to be actioned by the team. The ticket must have the following information:
| Tickets in this column are ready to be actioned by the team. (We should to agree on a definition of ready)
The ticket must have the following information:
· Description of requirements · Steps to reproduce**could be added to intake form./best practices for logging bugs). · Client · Business impact / Priority · Required by (?what is this) |
Blocked | If a task is dependent on any other group at TC. Please write a comment on what the blocker is. | If a task is dependent on any other individuals or group at TC, or there is a technical issue. ***Please write a comment on what the blocker is. Indicate who might to be engaged to help move things out of the blocked column. Keep comments in “plain English”. |
In Progress | Items in this column are being actively worked on by the team. Please make sure to assign the task to yourself. Only move a task to the next lane if the following conditions have been met:
| Items in this column are being actively worked on by the team. Please make sure to assign the task to yourself.
Only move a task to the next lane if the following conditions have been met:
· When applicable, documentation added to Confluence · When applicable test plan/cases have been defined. · Applicable functional testing passed. · Applicable regression testing passed. · Applicable UX testing passed. · Change / Code reviewed by another team member · Code changes are deployed to development · Functional test has passed testing, through the interface, by another team member (Acceptance criteria** are met. |
Review | Item has been addressed/fixed and is awaiting review by QA and/or DSD-CIVAV.
If any test fails, re-assign the card back to dev to investigate & move to the top of the To Do (Approved) column.
| Item has been addressed/fixed and is awaiting review by client. Testing by client/requester Only move to deploy if client agrees requirements are met/acceptance criteria are met If any test fails, re-assign the card back to dev, with a comment (@) in the discussion regarding the details, to investigate & move to the top of the To Do (Approved) column. |
Deploy | Items in this column have been tested and are waiting on the change management flow to be completed (i.e. change request is pending). |
|
Done |
| Agree on a definition of Done |