What is Kanban? Understanding Kanban an Agile Framework - Agile Digest
Вставка
- Опубліковано 6 чер 2024
- In this video, we'll dive into the Kanban framework, an Agile methodology that emphasizes continuous delivery, flexibility, and customer satisfaction.
We'll explore the core principles of Kanban, including visualizing work, limiting work in progress, and managing flow, and discuss how they can be applied to different types of projects and teams. You'll also learn about the benefits of using Kanban, such as increased productivity, faster cycle times, and better quality.
Looking to implement Kanban in your organization? Contact us now to book our Agile Transformation consultation and discover how we can help you successfully adopt this powerful Agile framework for your business.
--------------------------------------------------------------------------------------------------------------------------------------
Link to the Article: us.agiledigest.com/kanban/
A smart commentator who understands from what he is talking from a business perspective. I am really impressed. 5 stars plus.
For such videos, there must be a LOVE button on youTube.
Thank you,😍
Excellent Video
This is one of the best videos on kanban I have seen. Well explanatory
Wonderfully Explain, it has answered most of the questions I had about using Kanban in my day to day operations
Crystal clear explanation. It answered most of my questions and also helped me to explain the concept to my team. Thanks Niladri.
Great video
Thank you so much Agile digest. You have been of tremendous help
Really Good Explanation of Kanban and Scram
Thank you.
Amazing stuff
MAN , you are simply AWESOME , over all the Internet your presentations are the Best in terms of simplicity and objectives , all the best
Excellent overview - thanks
Glad you enjoyed it
I like the way you present your agile digest videos they are comprehensive and cover all aspects from scratch. Please keep them coming
Great Great
Very informative.. Thanks for this video. 👍
So nice of you
Great 👍 work. Thanks
Very comprehensive. This has been very helpful for me. Great Video! 10 stars
Thank You
wonderfully explained. Thanks from my heart.
Great presentation. Beautiful graphic representation. Very helpful. Thanks for sharing.
Excellent Presentation. God bless you
Very good session on Kanban concepts. Thanks
The best explanation on Kanban
Amazing, The most simple and clear explanation. Thank you.
Thank you Mr. Niladri you are my Agile Guru. You have helped so many like me to understand Agile related concepts with practical examples and real time scenarios.
You are welcome
Very good, Kanban covered very well and neatly presented.
I like how you've done the video.
It's like I'm in a classroom training.
Keep it up!
Many thanks.
Thank You.
Again you rocked as always. Your all videos are really helpful. You make us understand concepts on very easy way to which others can understand. Thank you so much!
My pleasure 😊
Good infomation, explained in cool manner , easy to understand!!
A fascinating presentation! It really helped me to understand the subject. Thank you very much sir!
Thanks man. U saved me a lot !!
Really Rocked Nilathri , your explanation and real-life scenario eg, makes me clearly understand the concepts and i won't forgot as well.
Keep Going....Best wishes.
Very informative, thanks for your thorough explanation. very appreciated
Thank you.
Great Niladri.. its very nice well explained Thank You :-)
Excellent Presentation
Good one
Thanks
Thank you for explanation about Kanban and Agile
good explanation sir.. keep it up
Thank You
It was very helpful and simple explanation...😊
Thank you so much Niladri for such a crisp explanation, your contents are always helpful for me!
Happy to hear that!
Fantastic overview! Thanks
Very informative, Good job 👍!
Wonderful presentation.
I have been listening to your videos. Great explanation and in depth concepts. Loved your Scrum, Scaled Agile and Kanban Videos. Awesome, these are all next level compared to other Agile Certifications I have done.
Glad you like them!
Excellent explanation with the good presentation. The most important is, it is easily understandable for any one.
Very good one. I liked it very much especially cfd
Thanks for this!
I really liked it and useful
Thank you so much for providing this much of crystal clear
I have not liked it I loved it
Great presentation. So clearly explained without complicating..
Great Video. Very Useful. Thank You.
I have a question on the cumulative flow slide where you marked Lead Time from yellow to Blue. Isn’t it supposed to be from Yellow to Green ( Done) ( green is not there in graph though )?
Good Explanation. Made it very simple.
Great explanation with slides. learned a lot
Great tutor!
Helped me crack internal kanban exam.must see to understand kanban concepts
Suoerb clarity.
Thank You
Very good explanation thank you
very useful presentation, thanks a lot for sharing.
Well explained. Thank you
Very informative -- thank you!
Thank You
Great! Thanks!
Brilliant Stuff.
Wonderful presentation..Thanks a lot.It is really helpful.
You are most welcome
Thank you very much!
Good Job Sir !! Kudos !!
This was great! However, you confused me on CFD. Cycle time and Lead time arrows (endpoints) are not in sync with what you are describing. The colors are: yellow, orange, blue, and pink. 1. You say cycle time is from red (pink) to blue, but the arrow shows from red (pink) to orange which represents DEV - QA. 2. You say from Blue to end of UAT is the Lead time but the arrow shows end of UAT to beginning of Backlog. So what is it? Let me know. WIP is correct. Again great job!!
Nicely Explained, easy to understand. Thanks a lot Niladri Bhai
+Deepak Mishra Thank you for your feedback. Glad to know you liked the video.
Great presentation and great slides. Hat off :)
Hey man you are really awesome,, billion thanks for this session
Well explained.
Thank You
Great explanation and presentation as always. I was looking for such an intro video on Kanban. However I have a question. Since backlog items can come from multiple sources and there is no PO to prioritize the backlog, how the dev team will pick "one" item if thats the only allowable number as per their WIP limit at present. Its possible that there are multiple items lying in backlog marked as highest priority - since they all come from different source and hence marked that way as per specific business community.
in few cases, there are someone there who guide to pick the PBIs. The team is self organized and should be able to take the most important item first and follow finish first approach. The Team can define class of services to cater high priority, Time bound or Intangible items to optimize the pull based system. Even If the inflow of high priority tickets are too much, the team can best perform by using the WIP limit, The team can increase the member count or can create another team to manage unexpected big numbers of high priority issues. Every day the team can have a Sync meeting of 15 minutes to make the strategy of the day keeping the backlog and in progress items with respect to their class of service.
Awesome explanation.. cant ask for better one. Gr8
superb piece of information shared Thanks!
Thank u very much sir very helpful 👍 😊
Excellent video, good job !
Utmost clarity achieved today....1 question though if possible.....what if the DEV WIP is full and Test WIP tested finds bugs and have to be pull back to DEV WIP.
Very good presentation
Thank You
Awesome video!
Glad you enjoyed it
Hello thank you for sharing your knowledge, I have a question.
What does UAT mean?
User Acceptance Test
UAT stands for User Acceptance Testing. This is typically the testing done by client users, before they give a go ahead for deployment in production
Excellent Presentation sir
Thank You
Agile Digest, Love your videos. Can you please update your playlists? Right now playlists have incorrect videos in them.
sure will have a look and update.
Next month I join a company they are using kanban. So I need some idea about kanban.thanks for sharing some idea
Best of luck
Crystal clear and straight to the point, good job sir
Thanks for the video. I need to know what if there is a bug, would tester move the story to the Dev - wip again? Because you mentioned in the beginning that stories moves from left to right only. How the bug will be handled? Further, if developer's wip limit is already reached and tester has to introduce a bug about stories then Dev - wip will face overflow. Thanks again.
Ashish, There are many ways on working on this situation. the WIP Limit is just to managed the flow with best optimized way. the goal is to complete the story as a whole from left to right side. if the story is currently at testing Phase and a Bug is created. That Bug can by created as child (subtask) of the story, the Bug/Subtask you can call as Story defects. It will be raised under the column where it will get fixed, generally "development" column (The defect can also go to backlog or todo based on the priority or severity). The WIP Limit you can configure to Include or not include the subtasks. The ALM tools will show the column as Red, if it is crossing the limit, that indicate the entire team (not only developer) needs to focus on that column to close the newly created defects, and bring down the total work items under defined limit for that column. The Tester will keep the story on the column of testing if the exit criteria of that columns restrict to move the story forward.
for example : The Exit Criteria for testing column can be "All P1 and P2 has to be resolved". So if the defect is P3 or P4, You can still go ahead and move the story as testing done.
Thanks for quick reply!
About "The Exit Criteria for testing column can be "All P1 and P2 has to be resolved". So if the defect is P3 or P4, You can still go ahead and move the story as testing done.", you mean even if we have bugs we can move the story in the testing done, but main story will be moved to UAT when even the defects are fixed?
What if the task is moved to complete and a month later there comes a issue on that task? Would we create a subtask in that scenario too?
How do we manage the exit criteria?
Can you share your contact number if possible? I would highly appreciate that.
Please Send us a mail at support@agiledigest.com.
I have a Software Maintenance Project where we work on Tickts and small enhancements.Can you let me know whether i can use Kanban for Daily Tracking.Also How do i generally choose between KANBAN vs SCRUM
Hi Veronica,
The basic criteria to select Scrum and Kanban is
If you can plan for two to threes weeks and fridge the commitment for two to three weeks. You can go with Scrum. where your deliverable will be delivered at the end of every sprint (ideally 2 or 3 weeks). with a same cadence sprint over sprint.
But if you have work for Production support, or your works demand frequent release (1 or multiple time in a week), adhoc requests, frequent change on priority, etc, using Kanban will be better approach here.
If you work for both enhancement and support, I suggest to separate the nature of work between two teams (scrum & Kanban) if possible.
This is very generic answer. There are many practical scenarios to take the decision, how best we can structure the team and approach .
if the kanban board miss to do and acceptance or estimation column what will be the effect??
Great presentations. In Kanban are there Story points ?
No.
Are the metrics available also in AZure DevOps where Kanban Board Integrated?
Not yet
Niladri, we are introducing Kanban and my team size is 7. My question is work in limit you mentioned as not more than 4 is it for the complete team. Am I understanding it correct? Please clarify. Iam new to Kanban.
For each team member, the WIP limit should be min 2 and max 5. You should start with the WIP limit at 3 for the team member.
@@user-vh5hs1vu6c, got it. Thank you !
As always, very informative video. Thanks. Will just be more user friendly if you fix your photo/video at certain portion of the screen.
Thanks!
you are welcome
Why was the scope portion deleted ?
Not sure which scope portion you are talking about, Can you please elaborate ?
Hi, thanks for the explanation it's awesome. I have question : if we take your example WIP in dev is 4 and it's full and in testing WIP is 3 and the testeur find bug from the last user story. how we manage this situation ? the dev related to this story will stop what he is doing and fix the bug or we should document all bugs and take it when we have room ? and it's same question when we get to UAT shall we stop all so it goes to dev and tester ? thanks
WIP is applied on User story, The defects are either child of that user story or and Independent Bug. If its a child of user story it will not impact the WIP, If its a independent bug, it will wait in the backlog
Have clarity in thoughts. Yourself seem to be confused, add to it focus on bettering Grammar.
i don't agree with the movies and park example used as the KANBAN board is not time boxed and the numbers of tasks pick up is regulated by the WIP limit. my take
Any suggestions for the viewers?
Nice video , but I think its better to use real software projects examples than park or movie theatre. .
Agree
Kanman Method by DA not kANBAN Toyota !
Great explanation but English grammar threw me off a little.
Amazing from the knowledge front, presenting way could be better.
Struggling for words. Not a good way of presentation. Not a great orator. The basics of Kanban could have been explained in a better way.
Thank you Sudha for your feedback. We all have opportunities to improve.