Project Victor Learning Hub
Menu
Get Certified
Get Certified

KANBAN

Understanding Kanban in Project Management

Kanban is a visual workflow management method that originated in manufacturing and has been widely adopted in Agile project management. It provides a framework for managing tasks, improving team efficiency, and ensuring work flows smoothly from initiation to completion.

What is Kanban?

Kanban is a Japanese term meaning “signboard” or “visual signal.” In project management, it refers to a system that uses visual cues, such as cards on a board, to represent tasks. The primary goal of Kanban is to optimize workflow, limit work in progress (WIP), and enhance overall productivity.

Principles of Kanban

  1. Start with What You Do Now: Implement Kanban on top of existing processes without major disruptions.
  2. Pursue Incremental Change: Encourage small, continuous improvements rather than drastic changes.
  3. Respect Current Roles and Responsibilities: Use Kanban to enhance existing team structures.
  4. Encourage Leadership at All Levels: Foster decision-making and leadership throughout the team.

Elements of Kanban

  1. Kanban Board: A visual representation of the workflow with columns representing stages such as “To Do,” “In Progress,” and “Done.”
  2. Kanban Cards: Visual markers representing tasks or work items.
  3. Work-In-Progress (WIP) Limits: Caps on the number of tasks in each stage to prevent overload.
  4. Cycle Time: The time taken for a task to move from start to finish.
  5. Lead Time: The total time from when a task is requested to when it is completed.

Steps in a Kanban Workflow

  1. Visualize Workflow: Use a Kanban board to map out stages of the workflow.
  2. Set WIP Limits: Determine the maximum number of tasks allowed in each stage to maintain focus.
  3. Manage Flow: Monitor tasks and identify any bottlenecks.
  4. Make Policies Explicit: Clearly define rules for moving tasks between stages.
  5. Implement Feedback Loops: Conduct regular reviews to refine processes.
  6. Improve Continuously: Analyze data to identify areas for improvement.

Setting Work-In-Progress (WIP) Limits

To set effective WIP limits:

  • Assess team capacity and historical data.
  • Set limits for each stage of the workflow based on the team’s ability to complete tasks.
  • Adjust limits based on observed bottlenecks or inefficiencies.

Measuring Cycle Time and Lead Time

  • Cycle Time: Tracks how long a task spends in active work stages (e.g., “In Progress” to “Done”).
  • Lead Time: Measures the total time from task creation to completion (e.g., “To Do” to “Done”).

Difference Between Cycle Time and Lead Time

  • Cycle Time focuses on task execution.
  • Lead Time includes both waiting and execution time.

Practical Examples of Kanban in Project Management

Example 1: Software Development

  • Scenario: A development team uses Kanban to manage feature delivery.
  • Workflow: Stages include “Backlog,” “Development,” “Testing,” and “Deployment.”
  • Usage: WIP limits ensure developers focus on finishing tasks in “Development” before starting new ones, preventing bottlenecks in “Testing.”

Example 2: Marketing Campaign Management

  • Scenario: A marketing team uses Kanban to plan and execute campaigns.
  • Workflow: Stages include “Planning,” “Content Creation,” “Approval,” and “Published.”
  • Usage: WIP limits in “Approval” ensure that the review team isn’t overwhelmed, speeding up campaign delivery.

Example 3: IT Support

  • Scenario: An IT support team uses Kanban to track service requests.
  • Workflow: Stages include “New Tickets,” “In Progress,” and “Resolved.”
  • Usage: Monitoring the “In Progress” stage ensures tickets are addressed efficiently, reducing response times.

Case Study: Kanban in a Project in Thailand

Project: Digital Transformation for a Retail Company

  • Scenario: A retail company in Thailand adopted Kanban to manage a digital transformation project involving website redesign and system integration.
  • Workflow: Stages included “Requirements Gathering,” “Development,” “Testing,” and “Implementation.”
  • Challenges: Bottlenecks in “Testing” delayed progress.
  • Solution: WIP limits were applied to “Development” to prevent overwhelming testers. Daily stand-ups and retrospective meetings addressed issues quickly.
  • Outcome: The project was delivered on time, with improved collaboration and transparency.

Example Kanban Board

Conclusion

Kanban is a versatile and powerful framework for managing workflows in Agile project management. By visualizing work, setting WIP limits, and continuously improving processes, teams can enhance productivity and ensure timely delivery of projects. Whether it’s software development, marketing, or IT support, Kanban provides a flexible approach to achieve better outcomes.

Cumulative Flow Diagrams

Understanding Cumulative Flow Diagrams in Agile

Cumulative Flow Diagrams (CFDs) are powerful tools in Agile project management, providing a clear visualization of workflow and progress over time. They help teams track progress, identify bottlenecks, and ensure that work is flowing smoothly through different stages of a process.

What is a Cumulative Flow Diagram?

A Cumulative Flow Diagram is a stacked area chart that represents the state of work items (e.g., user stories, tasks) in various stages of the workflow. It is plotted with:

  1. X-axis: Time (days, sprints, or iterations).
  2. Y-axis: The cumulative number of work items.

Each colored band in the diagram corresponds to a specific stage of the workflow, such as “To Do,” “In Progress,” “Review,” and “Done.”

How to Use a Cumulative Flow Diagram

  1. Track Workflow Progress: Monitor how work items progress through different stages over time.
  2. Identify Bottlenecks: Analyze areas where the bands widen (indicating tasks piling up) or narrow (indicating insufficient throughput).
  3. Measure Throughput: Evaluate how quickly work items are being completed.
  4. Forecast Delivery: Predict when the remaining work will be completed by examining trends in the “Done” band.

Practical Example of Cumulative Flow Diagram Usage

Scenario: A Sprint in a Software Development Project

  • Workflow Stages: To Do, In Progress, Testing, Done.
  • Team Goal: Develop and test features for a new application release.
  • Timeline: 10 days.

Day 1: The sprint begins with 20 tasks in the “To Do” column.

Day 5: 10 tasks move to “In Progress,” while 5 are completed and moved to “Done.”

Day 10: All 20 tasks are completed, with some passing through “Testing” before being marked as “Done.”

A Cumulative Flow Diagram for this scenario shows the smooth progression of tasks through the workflow stages. Any stagnation (e.g., a widening “In Progress” band) indicates a bottleneck.

Benefits of Cumulative Flow Diagrams

  1. Transparency: Provides a clear visual representation of team performance and workflow efficiency.
  2. Early Problem Detection: Highlights bottlenecks and areas needing attention before they impact deadlines.
  3. Continuous Improvement: Helps teams refine processes by identifying inefficiencies and improving flow.

Identifying Bottlenecks with CFDs

  • Widening Bands: A growing “In Progress” band indicates too many tasks started without sufficient resources to complete them.
  • Flat Bands: A stagnant “Done” band suggests work is not moving to completion, possibly due to delays in testing or review.
  • Narrow Bands: A consistently thin “To Do” band may indicate insufficient work is being planned or added to the pipeline.

Example:

In a CFD, if the “Testing” band widens significantly, this could signal a bottleneck in the testing phase. This may require reallocating resources, automating tests, or addressing dependencies to speed up the workflow.

Sample Cumulative Flow Diagram

The diagram should show distinct colored bands for each workflow stage, with time on the X-axis and cumulative work items on the Y-axis. It will illustrate how work progresses and highlight any potential bottlenecks.

Key Considerations When Using Cumulative Flow Diagrams

  1. Update Regularly: Ensure the CFD reflects the latest workflow data to provide accurate insights.
  2. Focus on Trends: Use the diagram to spot patterns rather than focusing on day-to-day fluctuations.
  3. Address Bottlenecks Quickly: Take corrective action as soon as bottlenecks are identified.

Conclusion

Cumulative Flow Diagrams are invaluable in Agile for visualizing progress, tracking workflow efficiency, and identifying bottlenecks. By leveraging CFDs, teams can ensure a smoother flow of work, improve delivery timelines, and foster continuous improvement.