Kanban Software Development
Kanban is not an agile methodology in the strictest of terms, but an approach for planning and executing the work in an orderly manner. A popular form of Agile development is the utlization of both the Scrum framework and a Kanban planning and execution process.
The word Kanban is of Japanese origin and its meaning is linked to a time concept, “just-in-time”. In practice, the Kanban method exists in a board or table (Kanban board), divided into columns, that shows every flow of the software production. As the development evolves, the information contained in the table changes, and when a new task comes into play, a new “card” is created.
The Kanban method requires communication and transparency so that the members of a team can know exactly at what stage the development is and can see the status of the project at any time.
Ability to view all tasks of one project (Completed, In Progress or In Testing, for example);
It is possible to limit the number of running tasks (that is, the amount of work, bearing in mind its resolution or deliverability);
Focus on the duration of a cycle – how long it takes a task to go from backlog to the final stage;
Allows continuous deliveries.
It is possible for members of a team to misinterpret the information show on the Kanban Board, especially when it is revealed as outdated;
Since there are no timeframes in Kanban, you can face time related problems, such as delays, associated with each and every stage.