Originating from lean and other just-in-time processes, Kanban is a scheduling tool. Kanban is a popular methodology created to implement agile and DevOps software development.

 

Now from whence did this Kanban come in picture?
Kanban has thus been removed from the lean manufacturing process. Kanban was created as a lean manufacturing technique made by Toyota.

Nowadays the same principle is being widely applied to software development. So it means the amount of work in progress matches the team capacity.

 

 

Manufacturing Instance

• Kanban is essentially a system utilising virtual cards, referred to as Kanban, that go from initiation to completion. The objective is to maintain a continuous flow of Kanban, ensuring that inventory is generated at the beginning of the process as needed at the conclusion. 

 

Development Instance

• We possess 20 backlogs/stories that must be finalized within the current sprint. As we commence addressing the backlog, we transition it through the stages of planned, in-progress, developed, tested, deployed, and completed. 
• We will establish our own Kanban board, a virtual platform, to organise all backlogs and endeavour to address them upon the completion of the sprint. It provides an excellent visual representation, a coherent workflow, a distinct emphasis, and gradual modifications over time.

 

 

Agile Features

Iterative and Incremental: Work is broken down into small, manageable cycles called iterations (e.g., sprints in Scrum). Each iteration aims to produce a working increment of the product.  
Customer Collaboration: Agile emphasizes close and continuous collaboration with the customer or stakeholders to ensure the product meets their needs.  
Responding to Change: Agile processes are designed to be flexible and adaptable to changing requirements, even late in the development cycle.  
Individuals and Interactions: Agile values individuals and their interactions over rigid processes and tools.  
Working Software: Working software is the primary measure of progress.  
Self-Organizing Teams: Agile teams are typically self-organizing and cross-functional, allowing them to make decisions and manage their work effectively.  
Continuous Improvement: Agile promotes regular reflection and adaptation to improve processes and team performance. 

 

 

Kanban Features

Visualise Workflow: Kanban employs a board (either physical or digital) featuring columns that denote various stages of the workflow. Tasks are depicted as cards that progress through various levels. This ensures openness and facilitates the identification of bottlenecks. 

Restrict Work in Progress (WIP): Kanban underscores the importance of establishing clear boundaries on the quantity of tasks at each phase of the process. This facilitates the completion of activities prior to initiating new ones, hence minimising multitasking and enhancing workflow. 

Manage Flow: The objective of Kanban is to ensure a seamless and uniform progression of work throughout the system. Bottlenecks and obstacles are recognised and resolved to enhance the flow. 

Articulate Process Policies: Kanban promotes the explicit definition and communication of the rules and policies that regulate the workflow. Establish Feedback Loops: Consistent feedback channels are crucial for ongoing enhancement in Kanban. Enhance Collectively, 

Progress Experimentally: Kanban advocates for implementing minor, incremental modifications to the process informed by data and feedback. 

Adhere to Existing Processes, Roles, Responsibilities, and Titles: Kanban can be integrated into current processes without necessitating substantial alterations to roles or structures at the outset. It seeks to enhance the existing system. Promote Leadership 

Initiatives Across All Tiers: Kanban empowers every team member to recognise and resolve challenges, cultivating a feeling of accountability and ongoing enhancement.