Wait, isn’t lead time the time when the ticket got created to when it went live? You explained cycle time instead if I am not wrong which is when the work started on the ticket to when it went live.
What you described as Lead Time is actually Cycle Time. Lead time is longer and starts with when a customer request has been made. Besides that, cool video, although there are way more ways to determine WiP, and we could also look at what´s the WiP when technically everybody can do everything ;-)
Concurrent work styles are the new sexy thing in engineering. But it is good to see, that you guys see it the same way. As line manager I always pushed for the serial production style. Do one thing at a time. You will be more focused and get the things done. Further your clients love it. Because you'll keep your promises for the due date.
There seems to be an obvious gap in explanation here. In the 4-6-2 WIP example, what happens when columns further to the right are holding things up due to their WIP limit? So testing is capped at 2, but developers complete another card but have nowhere to put it, and can't take a 7th card? It seems like there needs to be intermediate columns of backlog between each step in the workflow.
You could do that or maybe you could help out your tester so that they finish their work (cards) in order to free up space for another development card.
Adding intermediate backlogs is a natural inclination but will result in excess inventory of cards building up. Developers will continue to put cards into the intermediate backlog and testers will still only be able to handle 2 cards at a time and will never catch up. The concept is covered beautifully in the book The Goal: A Process of Ongoing Improvement. In this scenario, it seems like testers might be the system's constraint. To resolve this problem more testing capacity needs to be added either by borrowing developers for testing or hiring additional testers.
Great and simple video to help teams how to limit their WIP. Highly recommended! Btw, missing Chet Wrong videos, "The Wrong Way to do Agile", hilarious :-)
You have specialists for a reason. Does it make sense to teach your devs how to design? Unless they have that specific skillset already, isn't this a problem for the quality of the work coming out of your design team? As a designer, I'm pretty sure they don't want me doing their dev work. Small orgs w/ small teams on small projects need generalists. I get that, being I was one. But large orgs w/ large teams working on large projects will feel the impact of a poor user experience by cutting corners this way. You're just moving crappier work faster.
As a project manager, you don't always have control over number of WIP items in a specific column. For example, a developer/development team will finish many tickets on any given day and assign those to QA column. QA team(or even a single QA member) would then work through them at their own pace. WIP limits don't help with the natural workflow and planning of projects.
That is the goal of kanban. In this case, it is clear that you have a bottleneck in QA. Kanban with its WIP limits have shown it to you, so you know where to intervene :)
In Kanban the dev team shouldn't *assign* their complete to tasks to the QA column. Instead the dev team must just declare their work done and let the QA team *pull* the tickets into their column when they have capacity to do so. If QA never has capacity and no-one else can get tickets QA'd then eventually the dev team's column will become full as well, because there's no point developing endless things if no-one's testing them.
"Work in Process" is probably a better description, otherwise people tie this to an "In Progress" column instead of "The entire process from ideation to delivery". And, twice as many items as people seems kind of crazy - a team with 5 people should probably still work on 1 large item at a time, not 10 different small items at a time.
in czcams.com/video/zEJn6eQO6FE/video.html why did we place 4 for design and 6 for develop. I thought we were multiplying by 2? I don't get it or was this a typo?
Man who are you referring to when say 'teach other team members skills like design and testing'??? PM would teach designers to design and testers to test? Would you like to teach developers to develop? Super arrogant.
Damn Sacha, really dropped the ball on that one bro.
great teaching. The way you teach by doing simple stuff is magnificent
That demo with Sacha was perfect! This video was very useful. Thank you.
Wait, isn’t lead time the time when the ticket got created to when it went live? You explained cycle time instead if I am not wrong which is when the work started on the ticket to when it went live.
What you described as Lead Time is actually Cycle Time. Lead time is longer and starts with when a customer request has been made. Besides that, cool video, although there are way more ways to determine WiP, and we could also look at what´s the WiP when technically everybody can do everything ;-)
Concurrent work styles are the new sexy thing in engineering. But it is good to see, that you guys see it the same way. As line manager I always pushed for the serial production style. Do one thing at a time. You will be more focused and get the things done. Further your clients love it. Because you'll keep your promises for the due date.
I loved the ping-pong ball analogy. I'm going to use it with my team today.
We're sure your team will love it just as much 🙌🏻
Sasha is legit standing like a guy from a video game😂
Awesome vid, tomorrow I will have a meeting where I will propose wip limit and will use your example, thanks pal!
Fantastic Video.. Loved the simplistic way in which the concepts are explained..
There seems to be an obvious gap in explanation here. In the 4-6-2 WIP example, what happens when columns further to the right are holding things up due to their WIP limit? So testing is capped at 2, but developers complete another card but have nowhere to put it, and can't take a 7th card? It seems like there needs to be intermediate columns of backlog between each step in the workflow.
You could do that or maybe you could help out your tester so that they finish their work (cards) in order to free up space for another development card.
Adding intermediate backlogs is a natural inclination but will result in excess inventory of cards building up. Developers will continue to put cards into the intermediate backlog and testers will still only be able to handle 2 cards at a time and will never catch up. The concept is covered beautifully in the book The Goal: A Process of Ongoing Improvement. In this scenario, it seems like testers might be the system's constraint. To resolve this problem more testing capacity needs to be added either by borrowing developers for testing or hiring additional testers.
Patrice David Förster help out? What if you don’t know how?
Very good series on Kanban for beginners!
Simpel and great video, you made it easy for me to exaplain WIP for others, thanks.
Thanks for the video, straight to the point 👌
Great and simple video to help teams how to limit their WIP. Highly recommended! Btw, missing Chet Wrong videos, "The Wrong Way to do Agile", hilarious :-)
Thank you.... now I m able to correlate everything to my job.
Great analogy! Really helped to fully understand WIP
Thanks, a really useful series of videos, you explained kanban very clearly.
Glad to hear it!
Great teaching... Thanks for your wonderful lecture
Nice videos. However, the canned background music during dialog is a distraction.
3 x 2 = 4?
You have specialists for a reason. Does it make sense to teach your devs how to design? Unless they have that specific skillset already, isn't this a problem for the quality of the work coming out of your design team? As a designer, I'm pretty sure they don't want me doing their dev work.
Small orgs w/ small teams on small projects need generalists. I get that, being I was one. But large orgs w/ large teams working on large projects will feel the impact of a poor user experience by cutting corners this way. You're just moving crappier work faster.
makes sense.
Is that the definition of lead time? Normally that would be the difference between when you have something to do and when it starts to be done.
flawlessly explained wtf?
Awesome videos, man!
As a project manager, you don't always have control over number of WIP items in a specific column. For example, a developer/development team will finish many tickets on any given day and assign those to QA column. QA team(or even a single QA member) would then work through them at their own pace. WIP limits don't help with the natural workflow and planning of projects.
That is the goal of kanban. In this case, it is clear that you have a bottleneck in QA. Kanban with its WIP limits have shown it to you, so you know where to intervene :)
In Kanban the dev team shouldn't *assign* their complete to tasks to the QA column. Instead the dev team must just declare their work done and let the QA team *pull* the tickets into their column when they have capacity to do so.
If QA never has capacity and no-one else can get tickets QA'd then eventually the dev team's column will become full as well, because there's no point developing endless things if no-one's testing them.
Thank you so much for the videos, really help me so much :D
excellent presentation
PERFECT!
my boy Sasha though,, lol
otherwise I like the video also. Great information,
thnx!
"Work in Process" is probably a better description, otherwise people tie this to an "In Progress" column instead of "The entire process from ideation to delivery". And, twice as many items as people seems kind of crazy - a team with 5 people should probably still work on 1 large item at a time, not 10 different small items at a time.
Thank you so much for these videos. They are really helpful. ;)
Good Effort
Lovely!
1:05 Lav mic needs to be on camera-side, always
thanks!
Let Sasha SPEAK!!! I like SASHA!!!
1:30 Sasha's face..... "really brah??"
~3:00 Don't
Don't you mean 4 for Develop and 6 for Design?
He said you have 2 designers, 3 developers, and 1 tester. 2:42
too good
How was the number of cards arrived at?
Reeelax Sasha....
in czcams.com/video/zEJn6eQO6FE/video.html why did we place 4 for design and 6 for develop. I thought we were multiplying by 2? I don't get it or was this a typo?
He said you have 2 designers, 3 developers, and 1 tester. 2:42
Am I the only one who got lost on the WIP limit math with the post-its?
What if someone in the team is a developer as well as tester? Kind of a cross functional situation
WIP limits are set per stage of work, not per individual. The columns on the board should reflect how your work progress.
nice
Sascha looks sad. No wonder he does not work for Atlassian anymore
1:30 That’s not how things work
What is the name' s coach?
Max. He introduces himself in previous videos.
Mr Kanban
@@MacMcCaskill do you know his last name pls?
@@jorgeluiscastrotoribio650 his last name is kanban
bruh u need stop staring into my soul and focus a lil more on teaching me stuff
Man who are you referring to when say 'teach other team members skills like design and testing'??? PM would teach designers to design and testers to test? Would you like to teach developers to develop? Super arrogant.
this is cringe