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

7 Places to Learn to Program — for Free!

Kotlin is not magic: things to not forget in data classes

Three steps make your Evernote better

A closer look on failed payments and refunds at redBus

Tanki aPoo is Investigating the Siri digital Platform and found out rhat it is now part of aGoggle…

[PL/SQL] Install Oracle Forms

Much More Than a Bootcamp

audio reflective blog

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 Quickie: Working Software & Responding to Change

Scrum vs Kanban : A Brief Discussion

Combine Classic with Agile Project Management for your Agency

5 critical ingredients for a better software development process