Hindi
सिद्धांत
Kanban के सिद्धांत

Kanban के सिद्धांत: मूल नियम और Practices

<a className="txt-link" href="https://www.teachingAgile.com/about">Abhay Talreja</a>

द्वारा Abhay Talreja

4/1/2025

मेरा नवीनतम लेख - Empirical Process Control - The Key to Agile Success

Kanban के सिद्धांत और Core Practices की संपूर्ण गाइडKanban के सिद्धांत और Core Practices की संपूर्ण गाइड

Kanban एक powerful workflow management system है जो कुछ मूल सिद्धांतों पर आधारित है। इन सिद्धांतों को समझना Kanban को successfully implement करने के लिए essential है।

यह गाइड Kanban के सभी core principles और practices को विस्तार से explain करती है।

Quick Answer: Kanban के मूल सिद्धांत

CategoryPrinciples
Change Management1. जहां हैं वहीं से शुरू करें
2. Incremental, evolutionary change
3. Current roles का respect करें
4. सभी levels पर leadership encourage करें
Service Delivery1. Customer की needs पर focus करें
2. Work manage करें, workers नहीं
3. Policies review करें regularly
Core Practices1. Visualize
2. Limit WIP
3. Manage Flow
4. Make Policies Explicit
5. Implement Feedback Loops
6. Improve Collaboratively

Change Management Principles

Kanban की सबसे unique बात यह है कि यह existing processes को disrupt नहीं करता। ये चार principles बताते हैं कि Kanban change कैसे approach करता है।

1. जहां हैं वहीं से शुरू करें (Start With What You Do Now)

मतलब:

  • Current workflow को visualize करें
  • Existing processes respect करें
  • Revolutionary changes avoid करें
  • Incremental improvement focus

क्यों important है:

  • Change resistance कम होती है
  • Learning curve gentle है
  • Quick wins possible हैं
  • Team buy-in easier है

Practical Steps:

StepActionExample
1Current workflow map करेंStages identify करें
2Work types list करेंFeatures, bugs, tasks
3Existing roles document करेंWho does what
4Pain points identify करेंBottlenecks, delays

Example:

Current State Analysis:
┌─────────────────────────────────────────────────┐
│  Request → Analysis → Dev → Test → Deploy      │
│     ↑                                           │
│     └── Start यहीं से करें, process change     │
│         करने का प्रयास न करें                   │
└─────────────────────────────────────────────────┘

2. Incremental, Evolutionary Change

मतलब:

  • Small, manageable changes करें
  • Measure करें, फिर adjust करें
  • Big-bang transformations avoid करें
  • Continuous improvement embrace करें

Evolution Pattern:

Week 1: Visualize current work

Week 2-4: Add initial WIP limits

Month 2: Refine based on data

Month 3+: Advanced practices

Ongoing: Continuous improvement

Key Characteristics:

CharacteristicDescription
Safe to failSmall experiments low risk
Data-drivenChanges based on metrics
ReversibleEasy to roll back
SustainableTeam can absorb changes

3. Current Roles का Respect करें

मतलब:

  • Job titles न बदलें initially
  • Responsibilities respect करें
  • Authority structures maintain करें
  • Gradual role evolution allow करें

Comparison with Scrum:

AspectScrumKanban
RolesPrescribed (PO, SM, Dev)No prescribed roles
TitlesMay need changingKeep existing
ResponsibilitiesDefined by frameworkDefined by team
EvolutionRequired upfrontGradual over time

Benefits:

  • ✓ Lower resistance
  • ✓ Faster adoption
  • ✓ Existing expertise leveraged
  • ✓ Political conflicts avoided

4. सभी Levels पर Leadership Encourage करें

मतलब:

  • Top-down mandate नहीं
  • Everyone can suggest improvements
  • Distributed decision-making
  • Empowerment over control

Leadership Behaviors:

LevelLeadership Actions
IndividualIdentify improvements, speak up
TeamExperiment, share learnings
ManagementEnable, support, remove blockers
OrganizationVision, resources, culture

Service Delivery Principles

ये principles बताते हैं कि Kanban work और customers को कैसे approach करता है।

1. Customer की Needs पर Focus करें

मतलब:

  • Customer value priority
  • End-to-end flow optimize करें
  • Feedback loops maintain करें
  • Service orientation

Customer Focus Elements:

ElementDescriptionMetric
ValueWhat customer needsCustomer satisfaction
SpeedTime to deliveryLead time
QualityDefect-free deliveryDefect rate
ReliabilityPredictable deliveryOn-time delivery %

2. Work Manage करें, Workers नहीं

मतलब:

  • Focus on flow, not people
  • System optimization over individual productivity
  • Policies guide behavior
  • Collaborative problem-solving

Shift in Perspective:

TraditionalKanban
"Who is slow?""Where is the bottleneck?"
"Assign more work""Limit WIP"
"Work harder""Work smarter"
"Individual metrics""Flow metrics"

3. Policies को Regularly Review करें

मतलब:

  • Rules evolve over time
  • Regular policy discussions
  • Data-driven adjustments
  • Continuous refinement

Review Cadence:

Policy TypeReview FrequencyExample
WIP LimitsMonthlyAdjust based on flow
Definition of DoneQuarterlyUpdate quality criteria
Service ClassesQuarterlyRefine prioritization
Board DesignAs neededAdd/remove columns

छह Core Practices

Kanban Method में छह core practices हैं जो daily work को guide करती हैं।

Practice 1: Visualize (Work को दृश्यमान बनाएं)

Purpose:

  • Invisible work visible बनाएं
  • Shared understanding create करें
  • Problems surface करें
  • Communication improve करें

Essential Elements:

ElementDescription
BoardPhysical या digital representation
ColumnsWorkflow stages
CardsWork items
PoliciesRules और criteria

Example Board:

┌──────────┬──────────┬──────────┬──────────┬──────────┐
│ Backlog  │ Analysis │   Dev    │  Test    │   Done   │
│          │  WIP: 3  │  WIP: 5  │  WIP: 3  │          │
├──────────┼──────────┼──────────┼──────────┼──────────┤
│  [Card]  │  [Card]  │  [Card]  │  [Card]  │  [Card]  │
│  [Card]  │  [Card]  │  [Card]  │          │  [Card]  │
│  [Card]  │          │  [Card]  │          │          │
│  [Card]  │          │          │          │          │
└──────────┴──────────┴──────────┴──────────┴──────────┘

Visualization Best Practices:

  • Work types color-code करें
  • Blocked items highlight करें
  • Age indicators use करें
  • Dependencies show करें

Practice 2: Limit Work in Progress (WIP)

Purpose:

  • Focus improve करें
  • Multitasking reduce करें
  • Bottlenecks expose करें
  • Flow optimize करें

WIP Limit Benefits:

BenefitExplanation
Reduced lead timeLess work = faster completion
Better qualityMore focus = fewer mistakes
Earlier problem detectionBottlenecks visible quickly
Increased predictabilitySteady flow = reliable estimates

Setting Initial WIP Limits:

Formula: Team members + 1 या 2

Example:
- 5 developers
- Initial WIP = 5-7 items in "Development" column

WIP Limit Adjustment:

ObservationAction
Column always fullConsider increasing limit
Column often emptyConsider decreasing limit
Bottleneck persistentAddress root cause first
Steady flowLimits are good

Practice 3: Manage Flow (प्रवाह प्रबंधित करें)

Purpose:

  • Work smoothly move होना चाहिए
  • Bottlenecks identify और address करें
  • Lead time reduce करें
  • Predictability improve करें

Flow Metrics:

MetricDefinitionGoal
Lead TimeRequest से Delivery तकMinimize
Cycle TimeStart से Finish तकMinimize और stabilize
ThroughputCompleted items per periodOptimize
WIPCurrent work in progressControl

Flow Analysis:

Healthy Flow:
[Card] → [Card] → [Card] → [Card] → Done
   ↓        ↓        ↓        ↓
 Smooth   Smooth   Smooth   Smooth

Unhealthy Flow:
[Card] → [Card][Card][Card] → [Card] → Done
   ↓              ↓               ↓
 Smooth      Bottleneck!       Waiting

Bottleneck Resolution:

  1. Identify - Board पर कहां cards accumulate हो रहे हैं?
  2. Analyze - Root cause क्या है?
  3. Address - Solution implement करें
  4. Monitor - Improvement track करें

Practice 4: Make Policies Explicit (नीतियां स्पष्ट करें)

Purpose:

  • Shared understanding ensure करें
  • Consistent decisions enable करें
  • Conflicts reduce करें
  • Expectations clarify करें

Common Policies:

Policy TypeExample
Definition of Ready"Story में acceptance criteria होनी चाहिए"
Definition of Done"All tests passing, code reviewed"
WIP Limits"Max 3 items in Testing"
Pull Criteria"Pull highest priority first"
Escalation"Blocked > 2 days → escalate"

Policy Documentation:

┌─────────────────────────────────────────────┐
│              Board Policies                 │
├─────────────────────────────────────────────┤
│ ✓ Pull from right to left (finish first)   │
│ ✓ WIP limits are firm, not guidelines      │
│ ✓ Blocked items get red tag                │
│ ✓ Daily standup at 9:30 AM                 │
│ ✓ Review WIP limits monthly                │
└─────────────────────────────────────────────┘

Practice 5: Implement Feedback Loops

Purpose:

  • Learning enable करें
  • Improvements identify करें
  • Course corrections allow करें
  • Alignment maintain करें

Kanban Cadences (Common Feedback Loops):

CadenceFrequencyPurpose
Daily StandupDailyFlow status, blockers
Replenishment MeetingWeekly/Bi-weeklyWork prioritization
Service Delivery ReviewBi-weeklyCustomer satisfaction
Operations ReviewMonthlyCross-team coordination
Risk ReviewMonthlyRisk identification
Strategy ReviewQuarterlyDirection alignment
RetrospectiveBi-weekly/MonthlyProcess improvement

Effective Standups:

Focus on the Board, Not People:

❌ "John, आपने कल क्या किया?"
✓ "यह card 3 दिन से In Progress में है - क्या blockers हैं?"

❌ "सबको बताओ अपना status"
✓ "Right to left, कौन से items move हो सकते हैं?"

Practice 6: Improve Collaboratively (सहयोगात्मक सुधार करें)

Purpose:

  • Team-driven improvements
  • Shared ownership
  • Sustainable change
  • Continuous learning

Improvement Approaches:

ApproachDescription
ExperimentsSmall, safe-to-fail changes
RetrospectivesRegular reflection sessions
KaizenContinuous small improvements
A3 Problem SolvingStructured problem analysis

Improvement Cycle:

    ┌─────────────┐
    │  Observe    │
    └──────┬──────┘

    ┌─────────────┐
    │  Analyze    │
    └──────┬──────┘

    ┌─────────────┐
    │  Experiment │
    └──────┬──────┘

    ┌─────────────┐
    │   Learn     │
    └──────┬──────┘

    ┌─────────────┐
    │   Repeat    │
    └─────────────┘

Experiment Template:

┌─────────────────────────────────────────────┐
│             Improvement Experiment          │
├─────────────────────────────────────────────┤
│ Hypothesis: अगर हम WIP limit 5 से 4        │
│             करते हैं, तो cycle time         │
│             reduce होगा                      │
│                                             │
│ Duration: 2 weeks                           │
│                                             │
│ Metrics:                                    │
│   - Cycle time (before/after)               │
│   - Throughput (before/after)               │
│   - Team feedback                           │
│                                             │
│ Decision: Keep, adjust, or revert           │
└─────────────────────────────────────────────┘

Practical Implementation

Implementation Roadmap

Phase 1: Foundation (Week 1-2)

DayActivity
1-2Current workflow map करें
3-4Work types identify करें
5-7Board design करें
8-10Initial WIP limits set करें
11-14Basic policies document करें

Phase 2: Adoption (Week 3-4)

ActivityFocus
Board launchTeam training
Daily standupsFlow-focused
WIP enforcementGentle but firm
Data collectionMetrics start

Phase 3: Optimization (Month 2+)

ActivityFrequency
Metrics reviewWeekly
WIP adjustmentMonthly
Policy refinementAs needed
RetrospectivesBi-weekly

Board Design Guide

Simple Board:

| Backlog | In Progress | Done |

Standard Board:

| Backlog | Analysis | Development | Testing | Done |

Advanced Board:

| Backlog | Selected | Analysis | Dev | Dev Done | Test | Test Done | Deploy | Done |

Metrics Dashboard

Essential Metrics:

MetricTargetCurrent
Lead Time< 10 days12 days
Cycle Time< 5 days6 days
Throughput8 items/week7 items
WIP≤ 1518

सामान्य गलतियां

गलती 1: WIP Limits नहीं लगाना

Problem:

  • "हम flexible रहना चाहते हैं"
  • Limits के बिना Kanban = Kanban नहीं

Solution:

  • किसी limit से शुरू करें
  • Comfortable से थोड़ा tight
  • Adjust करते रहें

गलती 2: Board को Update नहीं करना

Problem:

  • Stale board = useless board
  • Reality से disconnect

Solution:

  • Daily updates
  • Real-time अगर possible
  • Team ownership

गलती 3: Bottlenecks Ignore करना

Problem:

  • "Testing में हमेशा pile-up है"
  • Accept कर लेते हैं बजाय fix करने के

Solution:

  • Root cause analyze करें
  • Systemic solutions find करें
  • WIP limits use करें to highlight

गलती 4: Policies Unclear रखना

Problem:

  • "Done" का मतलब सबके लिए different
  • Inconsistent decisions

Solution:

  • Document करें
  • Board पर display करें
  • Regularly review करें

गलती 5: Metrics Ignore करना

Problem:

  • "हमें feelings से पता है"
  • Data-driven decisions नहीं

Solution:

  • Basic metrics track करें
  • Trends analyze करें
  • Decisions base करें data पर

निष्कर्ष

Key Takeaways

Change Management Principles:

  1. जहां हैं वहीं से शुरू करें
  2. Incremental changes
  3. Roles respect करें
  4. Leadership encourage करें

Service Delivery Principles:

  1. Customer focus
  2. Work manage करें, not workers
  3. Policies regularly review करें

Core Practices:

  1. Visualize
  2. Limit WIP
  3. Manage Flow
  4. Make Policies Explicit
  5. Feedback Loops
  6. Improve Collaboratively

Action Steps

आज करें:

  • Current workflow map करें
  • एक simple board बनाएं

इस हफ्ते करें:

  • WIP limits implement करें
  • Basic policies document करें

इस महीने करें:

  • Daily standups शुरू करें
  • Metrics tracking शुरू करें
  • First retrospective करें

याद रखें

Kanban simple है, लेकिन easy नहीं है। Principles समझना first step है, consistently apply करना real challenge है।

Practice करते रहें, improve करते रहें, और results आएंगे।

आगे पढ़ें

Mastering the Basics: An In-Depth Introduction to KanbanDive into the world of Kanban with this comprehensive introduction, covering its principles, benefits, and applications in various industries.
The History and Origins of Kanban: From Toyota to AgileExplore the complete history of Kanban from its origins at Toyota to modern Agile teams. Learn how this visual workflow system revolutionized manufacturing and software development.
Core Principles of Kanban: A Complete Guide for Agile TeamsMaster Kanban Principles with our comprehensive guide. Learn the 4 core principles, 6 practices, and implementation strategies for Agile teams.
Kanban Boards: The Ultimate Guide to Visual Work Management for Agile TeamsMaster Kanban boards with our comprehensive guide. Learn advanced implementation strategies, optimization techniques, and integration with Agile practices.
Kanban Cards: The Ultimate Guide to Visual Work Management for Agile TeamsMaster Kanban cards with advanced implementation strategies, optimization techniques, and integration with Agile practices for enhanced team collaboration.
WIP Limits in Kanban: The Ultimate Implementation Guide for Agile TeamsMaster WIP limits with our comprehensive guide. Learn advanced implementation strategies, optimization techniques, and proven practices to boost team throughput by 40%.
Kanban vs. Scrum: A Comprehensive Comparison for Agile TeamsExplore the key differences between Kanban and Scrum, two popular Agile methodologies, to determine which one is best suited for your team's workflow and goals.
Choosing Wisely: When is Kanban Better than Scrum?Understand the differences between Kanban and Scrum, and learn when it's advantageous to use Kanban for managing your projects. Discover scenarios where Kanban outperforms Scrum.