KANBAN
Kanban is another concept of managing software development. It is gaining more and more popularity nowadays. Kanban means a signboard in Japanese. Kanban is done visually using a board where one can follow the progress of development through the different phases of the project. It is said that human brain can intuit visual information 60,000 times faster than text.
Kanban allows you to have only limited amount of Items in a single phase of the Development (for example in In Progress or in Testing) and therefore it prevents the team from doing all at once. When a certain phase is full of Items also the previous phase gets blocked, because it can not push any item into the next (filled) phase of development. So the team has to focus on the bottleneck where the work is stuck first before doing anything else.
Kanaban allows the developers to take tasks to work at any time unlike Scrum where all the Product Backlog Items are being pushed into the Sprint Backlog during the Sprint Planning. In this situation the manager has less administrative work to do with planning and organizing developers times.
Kanban is another concept of managing software development. It is gaining more and more popularity nowadays. Kanban means a signboard in Japanese. Kanban is done visually using a board where one can follow the progress of development through the different phases of the project. It is said that human brain can intuit visual information 60,000 times faster than text.
Kanban allows you to have only limited amount of Items in a single phase of the Development (for example in In Progress or in Testing) and therefore it prevents the team from doing all at once. When a certain phase is full of Items also the previous phase gets blocked, because it can not push any item into the next (filled) phase of development. So the team has to focus on the bottleneck where the work is stuck first before doing anything else.
Kanaban allows the developers to take tasks to work at any time unlike Scrum where all the Product Backlog Items are being pushed into the Sprint Backlog during the Sprint Planning. In this situation the manager has less administrative work to do with planning and organizing developers times.