Kanban methodology

Kanban is a visual workflow system that lets teams manage work in a continuous “pull” flow by moving tasks through columns (e.g., To Do, Doing, Done) while limiting work in progress to expose bottlenecks and improve efficiency. Unlike Scrum—which organizes work into fixed‐length sprints with prescribed roles (Product Owner, Scrum Master, Development Team) and ceremonies (Sprint Planning, Daily Stand‑up, Sprint Review, Retrospective)—Kanban doesn’t prescribe time‑boxed iterations or specific events; it focuses on ongoing delivery and evolutionary process improvement.

In Kanban (Japanese word for "visual board") there is a list a tasks that must be made and they are being developed by order of priority. This priorities may vary depending on the needs of the project. There is no time defined for delivering a set of objectives, although each objective has a time set. It priorizes agility on completing objectives rather than having multiple of them at the same time (Work In Progress) It is mainly used in environments of offering product support.

Kanban is a visual workflow management methodology, originally developed at Toyota as a scheduling system for just-in-time manufacturing. Its principles have since been adapted for various sectors, most notably software development and project management.

At its core, Kanban uses cards (often on a board) to represent tasks. Each card moves through predefined columns, typically representing stages in a process like "To Do", "In Progress", and "Done". This visual representation helps teams monitor and optimize workflow, ensuring smooth progression of tasks from one stage to the next. Tasks are being developed by order of priority. This priorities may vary depending on the needs of the project. There is no time defined for delivering a set of objectives, although each objective has a time set. It priorizes agility on completing objectives rather than having multiple of them at the same time

Kanban's primary goals are to enhance efficiency and continuously improve processes. It operates on several key principles.

Visualize Work

At its core, "Visualize Work" means converting abstract tasks into visual representations. This visualization provides clarity on the status, progress, and potential bottlenecks within a process. Kanban transforms the intangible nature of tasks into something concrete and tangible, enabling teams to manage and optimize their workflow more effectively.

How is Work Visualized?

• Kanban Board: The most common tool for visualizing work in Kanban is the Kanban board. This board can be physical (using sticky notes on a whiteboard) or digital (using software tools). It's divided into columns, with each column representing a stage in the process.
• Cards: Each task or item of work is represented by a card. The card contains essential details about the task, like its description, owner, due date, and any other relevant information.
• Columns: As mentioned, each column on the board signifies a stage of the workflow. Common columns are "To Do", "In Progress", and "Done", but these can be customized to suit specific processes.
• WIP Limits: Though not solely about visualization, Work-in-Progress limits are often indicated at the top of columns. These numbers signify the maximum number of tasks/cards that can be in that column at any given time.

Benefits of Visualizing Work

• Clarity: Team members can instantly grasp the status of tasks, who's working on what, and what needs attention.
• Transparency: It promotes openness about the state of work, fostering trust and collaboration.
• Enhanced Communication: When every team member can see the state of all tasks, it reduces the need for status update meetings and encourages proactive discussions.
• Motivation: Visual progress can be motivating. Moving a task to the "Done" column can give a sense of accomplishment.
• Focus: With tasks laid out visually, it's easier for teams to prioritize and focus on the most pressing items.

Limit Work-in-Progress (WIP)

It is a foundational principle in the Kanban methodology. The concept is rooted in the belief that multitasking and overburdening a system or team diminishes efficiency and output quality. Limiting WIP means putting a cap on the number of tasks or items being worked on simultaneously at any given stage of a process. For instance, if a column on a Kanban board titled "In Progress" has a WIP limit of 3, then only three tasks can be in that column at any one time. It is about optimizing the system for flow and efficiency, ensuring that teams produce the best possible work in the shortest amount of time. It's a balance of not overloading the system while ensuring resources are effectively utilized.

Key aspects

• Focus: By restricting the number of concurrent tasks, teams can concentrate on finishing what they've started rather than constantly switching contexts.
• Reducing Wait Times: When too many tasks are in progress, it takes longer for any single task to be completed. Limiting WIP can reduce cycle times.
• Identifying Bottlenecks: If tasks consistently pile up in one stage of the process, it's an indication of a bottleneck or inefficiency that needs to be addressed.
• Maintaining Quality: Less multitasking means fewer mistakes and higher quality output.

Benefits

• Improved Flow: Tasks move smoothly from one stage to the next with minimal delays.
• Reduced Stress: With a clear focus and fewer tasks at hand, teams often feel less overwhelmed.
• Better Predictability: With consistent flow and reduced bottlenecks, it's easier to predict completion times.

Implementation

• Start with a Baseline: Teams often begin by setting an initial WIP limit based on current capacity or by making an educated guess.
• Adjust Over Time: Regularly review and adjust WIP limits based on the team's experiences and the flow of work. If tasks are consistently completed quickly and the team feels underutilized, the WIP limit might be too low. Conversely, if tasks are stagnating, the limit might be too high.

Challenges

• There might be resistance initially, especially if team members are used to juggling many tasks at once.
• It requires discipline. Teams must resist the urge to pull in new tasks before completing what's already in progress.

Manage Flow

Flow refers to the movement of work items through the production process. Managing flow involves observing, analyzing, and optimizing this movement to ensure work progresses smoothly and efficiently from inception to completion. It is all about ensuring that work progresses without unnecessary delays or obstructions. By constantly observing and adjusting the flow, teams can achieve faster delivery times, improve predictability, and ensure that capacity is used efficiently.

Key concepts

• Flow Efficiency: This is a measure of how much time a work item spends actively being worked on, compared to the total time it spends in the system (including waiting). Improving flow efficiency often means reducing wait times.
• Lead Time and Cycle Time: Lead time measures the duration from when a task is created until it's completed. Cycle time starts the clock when the team begins actively working on the task. Monitoring these times helps teams understand how long tasks take and where delays might occur.
• Feedback Loops: Effective flow management benefits from regular feedback. Short feedback loops help teams adjust quickly to changing conditions or recognize issues that impact flow.
• Making Policies Explicit: Clearly defining the criteria for moving a task from one column to the next can reduce ambiguity and ensure that work flows consistently.
• Balancing Demand with Capacity: Teams need to ensure they don't accept more work than they can handle. This balance helps in maintaining a consistent flow and preventing burnout.
• Visual Metrics: Using charts like Cumulative Flow Diagrams (CFDs) can provide visual insights into how work is flowing. These diagrams can reveal issues like growing lead times or bottlenecks.

Continuous improvement

Often known by its Japanese term "Kaizen", it is a philosophy and methodology that focuses on achieving regular, incremental improvements in processes, products, or outcomes. Rather than aiming for large, one-time leaps, continuous improvement emphasizes small, consistent changes that compound over time. It is an ongoing effort to enhance products, services, or processes by making regular, incremental improvements, which in the long run can lead to significant advancements and efficiencies.

Principles

• Customer Focus: Understand and prioritize the needs and values of the end-users or customers.
• Employee Involvement: Engage all members of an organization in the improvement process, since those closest to the work often have the best insights.
• Incremental Change: Instead of major overhauls, focus on small, manageable changes which are easier to implement and can lead to long-term improvement.
• Standardization: To recognize deviations and areas of improvement, you need a standard. Once an improvement is identified and tested, it becomes the new standard.

Tools and Techniques

• PDCA Cycle (Plan-Do-Check-Act): A systematic approach to problem-solving and improvement activities.
• 5 Whys: A technique used to drill down into the root cause of a problem by asking "Why?" multiple times.
• Gemba Walk: A management practice where leaders visit the actual work floor to observe processes and identify areas for improvement.
• Value Stream Mapping: A tool to visualize and analyze the flow of materials and information required to bring a product or service to the consumer.

Benefits

• Improved Efficiency: Regularly examining and refining processes can lead to waste reduction and better resource utilization.
• Increased Quality: By continuously addressing small issues, overall product or service quality improves.
• Enhanced Employee Morale: Engaging employees in the improvement process can lead to a more invested and empowered workforce.
• Competitive Advantage: Organizations that prioritize continuous improvement often adapt more quickly to external changes, keeping them ahead of competitors.

Culture

Continuous improvement is not just a toolset but a cultural shift. For it to be successful, it requires buy-in from all levels of an organization, from top management down to the front-line workers.