How to Calculate WIP Limits for Kanban (and Why You Should)

Поділитися
Вставка
  • Опубліковано 2 жов 2024

КОМЕНТАРІ • 16

  • @alexiskyung
    @alexiskyung 9 місяців тому +2

    Why don't you have more likes, it's really well explained in a practical way. Do you have a video with more practical examples of calculations of a cycle time, SLE, decrypt the CFD, etc. All the best for the new year 2024, hang in there with the good tips and in good health :)

  • @shamika326
    @shamika326 10 днів тому

    "Great content! It's awesome how channels like yours break down Scrum, Agile, and SAFe concepts for beginners like us. However, one thing I've noticed is that while we learn about various frameworks like daily standups, velocity charts, sprint retrospectives, and Agile Release Trains (ART), it's rare to see practical demos or templates for reports, charts, or meeting formats. It would be incredibly helpful if you could show real-world examples or templates of things like velocity charts, Agile Release Train planning, sprint reports, and even daily standup formats. It would really benefit learners like us who are trying to see how these concepts come to life in practice!"

  • @indiaendless7388
    @indiaendless7388 18 днів тому

    Please prepare a video on how to reduce bottleneck by amending the WIP limit

  • @ahallock
    @ahallock Місяць тому

    This seems like waterfall with handoffs at each step. I would argue you should only have one WIP item at a time. Finish the item completely (release to prod) before going to the next item.

  • @Alpheus2
    @Alpheus2 Рік тому +2

    Happy to hear you took some time to focus on family. Welcome back, Vibhor.

  • @sujathabhushanam8789
    @sujathabhushanam8789 11 місяців тому +1

    Vey clear explanation on WIP limits. Thank you so much for the video

  • @PawanKumar-bg8uj
    @PawanKumar-bg8uj 10 місяців тому +1

    Wonderfully explained as always. Thank you for sharing

  • @deusman4150
    @deusman4150 Рік тому +1

    I didn't get it. You said the data says that dev column gets 4 cards on average per month, then why would you multiply 4 into 4 to get 16? Dev is not competing 16 story's per month, according to you they are only competing 4 per month, that makes it 1 story per developer per month.

    • @VibhorChandel
      @VibhorChandel  Рік тому +1

      That's 4 items per month per person in the dev column. Missed by mistake. The purpose is to calculate the equivalent rate of delivering items for other columns.

    • @deusman4150
      @deusman4150 Рік тому

      @VibhorChandel ty for the reply. Another question please, why take the slowest column, is it because of the theory of constraint concept?

    • @eugenetorre6688
      @eugenetorre6688 3 місяці тому

      I got confused because of this as well ☺️

    • @indiaendless7388
      @indiaendless7388 19 днів тому

      ​@@eugenetorre6688mee too 😊

  • @nidhi8665
    @nidhi8665 11 місяців тому

    Hi Vibhor, need your input on Kanban maturity assessment

  • @ariaagile
    @ariaagile Рік тому

    It's great to see you again

  • @441rahul
    @441rahul Рік тому

    Happy to see you @vibhor,
    Glad to tell you I have used your WAHZUR method in many interview and got a great response. Thanks a lot,