Getting Started With Kanban

  1. Are all the items that the team is working on are present on the board, from bugs to maintenance task?
  2. The value of the ticket is only achieved when it is in production. So let the board reflect the process until production.
  3. Not everything present in Dev and Testing Column is being worked on. Some tickets are moved from previous columns because they were completed. Add buffers or queues to represent that.
  4. A ticket itself can be of different types. A new feature, bug, maintenance etc. Assign a colour for each type.
  5. Add details on the tickets like the description, tracking ids, deadlines, blockers (represented by a small red sticker on top), progress indicators (indicated by a dot).




Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Hashicorp Consul setup and it’s Integration with Proxysql

How to resolve wazuh ( cluster currently has [1000]/[1000] maximum shards open) error message

Rails configurations from S3

All the background research you need to get started with FLUTTER!!!

Transitioning to product management

Composing Knowledge

Connecting device to processor

Fixing Gluster’s git history…

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Siddhesh Nikude

Siddhesh Nikude

More from Medium

Agile Project Management

Organizing around Outcomes with OKRs and Scrum

Top Five Articles on December 7

Is it really ‘Done’?