Scrum addresses the software development where the requirements are frozen before the sprint starts, but what about the teams which work on dynamic requirements which can come at any time? For example in a team which works on technical tickets, these tickets may come at anytime and hence the sprint cannot be decided, estimation cannot be done and the velocity cannot be calculated. Kanban is the solution to all this. Started in Toyota, Japan this was introduced to increase the productivity of the factory. ‘KANBAN’ in Japenese, means a visual signal. Kanban was later used as an effective method in agile software development and it can be implemented in teams where requirements are not certain. The work items in this approach, are put on a board where each team members can access and update their work. The team can have a physical or virtual Kanban board. Colocated teams prefer to have a physical board. The basic function of the Kanban board is that the team can visualize thei