Can you think of a benefit of specialisation? Let me know in the comments below. Can you think of a DISbenefit of specialisation? Again, let me know in the comments below.
One issue is that if the specialized member/s is absent for any reason (sickness or disruptive workplace issues, for example), then the other team member/s may be unlikely to deliver the full service required by the role necessary.
Wow you explained this better than my professor in the university! I really like the idea of having difficult concept to be translated into daily lives like this video and it's just very easy to remember and understand in the long run. I just subscribed! thanks for the video ^^
your videos are perfect, they really put me out of a big trouble where I've had a huge tasksheet to do and I was struggling to understand it, this Kanban-Coffee-Shop example not only made me understand Kanban in its simplest ways, but also this Huge ex, sheet looks super easy for me now. Thank you soo much, Great work. waiting for upcomming videos.
with dedicated order taker and dedicated barista, you limit cross contamination from potentially handling cash and/or proximity to customers. In the same way, with dedicated developers for certain aspects of coding, you can limit risks by reducing their access to systems, to those particular to their tasks.
Being a barista without having customer interaction can be seen as an advantage, but I still would put it in the disadvantage box. A big advantage would be the ability to scale out (like hiring more barista's with only one (or more) order takers... a restaurant where the chef has to take the orders himself is a nice thing, but probably impractical).
One of the disadvantages of specialisation is the dependency or reliance of this specific resource or expertise in the value creation chain without which the process breaks down inevitably.
Benefits of specialization include that as each team member does something over and over they become experts. You can also hire a lesser skilled assistant at a lower wage rather than needing every team member to have gone to barista U. Specialization also helps focus. If there are 8 tasks to do total, and a couple of them are squarely in what everyone knows you're good at then it makes it easier to pick something. Automatically narrowing your focus is usually a good thing. There are also a lot of dangers with specialization. People can block others from helping or learning, refuse to do something that it outside of the specialty. It can be less about the total business goal, and more about doing things the right way, which is great, unless you go out of business from something outside of the control of the one specialist. I want to also pose a question about your evaluation of value. In the example is it assumed that the customer values minimized time once the order is placed. I would argue that the value is total time from entering the initial queue to order until they leave with their drink. If you could reduce total wait time by 10% by some efficiency gained by taking lots of orders at once and then cranking out production you might end up increasing wait time of the average order placed by 5%. What do you - does everyone think of this sort of consideration?
Love your advantages and disadvantages... ... and REALLY love the last point you made: the first queue is part of the system... and we should be optimising the system as a whole (as in your example).
Hi, Gary. Now I have arrived in 2020! And I wonder is there any improvements from the customers’ perspective in this coffee shop example after limiting WIP? Let’s say there are several people in the order queue. They all have the same aim that is to have a coffee so that they need to wait sequentially. The total waiting time of each customer has been determined once entering the order queue. This is because each customer still need to wait in the next queue one by one after the information has been recorded. So from this point of view, I would say for the efficiency of each customer buying a coffee would not be increased or reduced no matter if WIP is limited. There is only one difference that the customers may wait in different queues, but it does not a case for the customers cuz they only consider how long they can have a coffee in their hands.
Relevent or not, you just made my day! I'm a HUGE fan of french cleats and I used them for all sorts of applications. Good luck with your inspired implementation 👍👍👍
I like it. Very much. But I'd love to hear some pleasant music at the coffee shop 😉 Sometimes it's hard to say if sth is adventage or disadvantage. For whom? For individual, team, system? Some ideas: reaching the master level (and demanding a raise), smaller tendency to collaboration ("just doing my job"), differentiation of earnings, problems with temporary replacement in case of absence (sickness, motherhood), routine and job burnout.
Funny you should mention the music... because I thought to add it... and them completely forgot to do so! Like your advantages/disadvantages. And also like your question: "For whom?"
I just want to say thank you for what you do for us. I was wondering if you have and videos or if you could direct me to “Scrum Master job interviews?” I am sure you are the right person with this knowledge. Thank you.
Subscribed! I am really enjoying, and learning, from your videos. Please continue to do your great work. I would consider using a full service restaurant as an example. It meets all of your criteria and addresses some other comments. For example, in most full service restaurants diners pay AFTER they eat, not up front as in a coffee shop. Thus, the very real possibility of someone walking out without much notice plays directly into the potential of waste. And, if you're going to use a full service restaurant as an example then, really, it needs to be Hell's Kitchen. I can already here Gordon's voice during the test phase...
@@Developmentthatpays I don't think this is your best work. I don't want to insult you but maybe you have outgrown your subject matter. You have a way of uncomplicating concepts that I thank you for. You should be adored and I think your target audience is not being reached.
@@Developmentthatpays We'll Gary, given your experience and what's happening China, it would be interesting to understand how a Scrum Team/ methodology could be utilized to handle a disease outbreak even if it's just in theory. And to add to that making it a pull rather than a push to meet critical timing windows.
Pretty interesting that you show me the Japanese Chinese Chars. and I just understand what is Kanban from the phrase 看板 It is like "Rules or processes written on the board" which we have to follow. Yes, usually Japanese will follow this Kanban since they are very disciplined Every morning they come to work, have team meeting and look at the board with all the tasks and reviews the rules and processes and then start morning shift. There may be noon meeting after lunch. Before closing, they have another team meeting...
Thanks Gary. Another great video helping with my learning of all three 'kanban's, and an excuse for me to pull out my old Lego. The translation, from Japanese to English, for kanban is 'visual card/thing', so how did it end up being used for the framework and the principles? I think these de-value the first meaning. Try this test: "The Kanban Team moves the kanban across the kanban board, using kanban principles." The reason my dev team think I have lost my mind.
I have to agree with you. I do wish "Kanban-the-Agile-framework" was called something else. Not least because many Kanban-the-Agile-framework implementations have precious little "proper" (signal/sign, principles) kanban in them.
Just found this channel looking to prep for my PSK! Subbed :D I would think a benefit of specialisation is that the work can be done quickly (increasing throughput) as it is the expert performing the work, the downside could be a single point of failure should the expert get hit by the famous "lottery bus"...
CaptainTiguan so to rephrase the downside point if the Coffee Man is sick/ill and had to leave the shop does Doctor Who know how to continue queue and use the machine?
Peter Taylor Exactly that. And reinforcing the point that “development teams” need to be cross functional, 3 or more in number and able to tackle the vertical slice! Any specialist advice should be taken when sprint planning and managers can be made aware of any upskilling required.
Coffee, Martini, perhaps a Sandwich or a demand signal for World Health Organization for contagious disease outbreaks, Gary what subject matter works best for you?
@@Developmentthatpays It has been a great pleasure Mr. I am not Native English speaking, but I understood better than many exhibitors speaking in Spanish, it must be because you British express everything more clearly than other Citizens of the World, it is also that his teaching method is very appropriate, to learn more agilely . Thanks
I don't understand what's the point in creating a maximum work in progress to three cups. It just seems like an artificial way of making it seem like there's less work. All your doing is turning paying customers away who would've else paid us and waited for their coffee to be made. So I'm Looking into the insight of the functional purpose of wip, thanks.
It is that if we allow a big queue of upstream/early stage work (eg order taken/empty coffee cup in this example) to build up because the downstream/next stage process is slower/not keeping up, then we are creating massive potential scrap - work upstream can continue to be built in an incorrect way without realising it (you only find out it is scrap when the downstream process tries to add to the next piece of value). The kanban prevents this and also visibly and physically makes you resolve the issue of an imbalanced system that one way or another will in itself create problems eg the imbalance causes the barrista to become massively pressurised as they are behind schedule so start rushing/cutting corners to catch-up, etc..
@@alexclark5809 - Thank you for bringing up re-work; although I like this coffee shop example, it's not the best to highlight the dangers/costs or rework.
Hrm, I've had a though -- I know ... uncommon -- about the differences between Kanban within IT and Business, and I believe this may be something I've not appreciated in the past. Am I the only one here? *eek* If not, I'll stop chatting in this video. If so, let me know.
![[UA] Eternal Fire проти NAVI | EPL Season 20 Malta](http://i.ytimg.com/vi/chvlsDygrZM/mqdefault.jpg)
Can you think of a benefit of specialisation? Let me know in the comments below.
Can you think of a DISbenefit of specialisation? Again, let me know in the comments below.
ua-cam.com/video/W8dKoRjFvTY/v-deo.html
One issue is that if the specialized member/s is absent for any reason (sickness or disruptive workplace issues, for example), then the other team member/s may be unlikely to deliver the full service required by the role necessary.
@@themilesinkorea Exactly!
@@Developmentthatpays Not that I've ever seen a workplace issue, of course 😎. Enjoying your vids, DTP!
Excelent video. Kudos to the presenter for his great style deliverying!
Thank you!
Thank you for this fantastic video. Super well explained, while remaining entertaining. Very well done!
Wow you explained this better than my professor in the university! I really like the idea of having difficult concept to be translated into daily lives like this video and it's just very easy to remember and understand in the long run. I just subscribed! thanks for the video ^^
This video deserves an extra 10k likes!
Seriously, it’s so good!
Very helpful. Thanks for sharing your knowledge. Have a great weekend. ☕
Thank you! You too!
Mr. You are a Grand Master
your videos are perfect, they really put me out of a big trouble where I've had a huge tasksheet to do and I was struggling to understand it, this Kanban-Coffee-Shop example not only made me understand Kanban in its simplest ways, but also this Huge ex, sheet looks super easy for me now. Thank you soo much, Great work. waiting for upcomming videos.
Ceey good explanation for Kanban, thanks .
Really glad you liked it 👍
good content....i just read Bill Galvin on Kanban
with dedicated order taker and dedicated barista, you limit cross contamination from potentially handling cash and/or proximity to customers. In the same way, with dedicated developers for certain aspects of coding, you can limit risks by reducing their access to systems, to those particular to their tasks.
Being a barista without having customer interaction can be seen as an advantage, but I still would put it in the disadvantage box. A big advantage would be the ability to scale out (like hiring more barista's with only one (or more) order takers... a restaurant where the chef has to take the orders himself is a nice thing, but probably impractical).
Yes, I'd agree with those.
(You put an image in my mind of a chef - with his/her knives! - taking orders!)
Super helpful! Thank you!
Glad you found it useful 👍
One of the disadvantages of specialisation is the dependency or reliance of this specific resource or expertise in the value creation chain without which the process breaks down inevitably.
Excellent point: specialisation makes the system more fragile.
12:53 and you are also a mind reader! I quit drinking coffee over 6 months ago, and just started to think on getting a cup tomorrow.
🤣
Benefits of specialization include that as each team member does something over and over they become experts. You can also hire a lesser skilled assistant at a lower wage rather than needing every team member to have gone to barista U. Specialization also helps focus. If there are 8 tasks to do total, and a couple of them are squarely in what everyone knows you're good at then it makes it easier to pick something. Automatically narrowing your focus is usually a good thing.
There are also a lot of dangers with specialization. People can block others from helping or learning, refuse to do something that it outside of the specialty. It can be less about the total business goal, and more about doing things the right way, which is great, unless you go out of business from something outside of the control of the one specialist.
I want to also pose a question about your evaluation of value. In the example is it assumed that the customer values minimized time once the order is placed. I would argue that the value is total time from entering the initial queue to order until they leave with their drink. If you could reduce total wait time by 10% by some efficiency gained by taking lots of orders at once and then cranking out production you might end up increasing wait time of the average order placed by 5%. What do you - does everyone think of this sort of consideration?
Love your advantages and disadvantages...
... and REALLY love the last point you made: the first queue is part of the system... and we should be optimising the system as a whole (as in your example).
Thank you so much for this very useful video it helped me a lot for my exam !
You're most welcome! Best of luck with the exam.
Sorry, NOT an agile framework. It is a Method, and not an agile Method. Simply a Method.
Hi, Gary. Now I have arrived in 2020! And I wonder is there any improvements from the customers’ perspective in this coffee shop example after limiting WIP? Let’s say there are several people in the order queue. They all have the same aim that is to have a coffee so that they need to wait sequentially. The total waiting time of each customer has been determined once entering the order queue. This is because each customer still need to wait in the next queue one by one after the information has been recorded. So from this point of view, I would say for the efficiency of each customer buying a coffee would not be increased or reduced no matter if WIP is limited. There is only one difference that the customers may wait in different queues, but it does not a case for the customers cuz they only consider how long they can have a coffee in their hands.
Not really relevant, but i really love the idea of french cleat bookshelves. I will absolutey be making an "inspired implentimentation" in the future
Relevent or not, you just made my day! I'm a HUGE fan of french cleats and I used them for all sorts of applications. Good luck with your inspired implementation 👍👍👍
I like it. Very much. But I'd love to hear some pleasant music at the coffee shop 😉 Sometimes it's hard to say if sth is adventage or disadvantage. For whom? For individual, team, system? Some ideas: reaching the master level (and demanding a raise), smaller tendency to collaboration ("just doing my job"), differentiation of earnings, problems with temporary replacement in case of absence (sickness, motherhood), routine and job burnout.
Funny you should mention the music... because I thought to add it... and them completely forgot to do so!
Like your advantages/disadvantages. And also like your question: "For whom?"
@@Developmentthatpays You asked for feedback 😁 .You can count on me in this matter.
This is super helpful.
I just want to say thank you for what you do for us. I was wondering if you have and videos or if you could direct me to “Scrum Master job interviews?” I am sure you are the right person with this knowledge. Thank you.
Subscribed! I am really enjoying, and learning, from your videos. Please continue to do your great work.
I would consider using a full service restaurant as an example. It meets all of your criteria and addresses some other comments. For example, in most full service restaurants diners pay AFTER they eat, not up front as in a coffee shop. Thus, the very real possibility of someone walking out without much notice plays directly into the potential of waste.
And, if you're going to use a full service restaurant as an example then, really, it needs to be Hell's Kitchen. I can already here Gordon's voice during the test phase...
Following their excellent site
Nice point.
Thank you!
I'm not getting it. How is this any different specializing tasks on an assembly line?
Depends on the assembly line: very similar to a Toyota assembly line ("pull"); very different to a Henry Ford assembly line ("push").
@@Developmentthatpays Thanks. I will investigate further. 😄
Hi Gary, I received your email and clicked on the link... Good video, simple to understand and with a relevant every day example of Kanban. Subbed. 👍
Delighted that the video was relevant for you. And thanks for subscribing!
Gotta be honest Gary I haven't looked at a cup of coffee the same way for a while thanks to you, and that was true even before I saw this video :p
Kevin! How the devil are you? Hope life is treating you well. 👍
Gary, kanban is kanban. There is no capitalization in Japanese regardless of sign, principle or applied methodology. 看板
I don't disagree. The capitalisation is my own shorthand/convenience.
@@Developmentthatpays I don't think this is your best work. I don't want to insult you but maybe you have outgrown your subject matter. You have a way of uncomplicating concepts that I thank you for. You should be adored and I think your target audience is not being reached.
@@hollyjacobs7593 - What subject area would you like me to focus on?
@@Developmentthatpays We'll Gary, given your experience and what's happening China, it would be interesting to understand how a Scrum Team/ methodology could be utilized to handle a disease outbreak even if it's just in theory. And to add to that making it a pull rather than a push to meet critical timing windows.
Pretty interesting that you show me the Japanese Chinese Chars. and I just understand what is Kanban from the phrase 看板
It is like "Rules or processes written on the board" which we have to follow.
Yes, usually Japanese will follow this Kanban since they are very disciplined
Every morning they come to work, have team meeting and look at the board with all the tasks and reviews the rules and processes and then start morning shift.
There may be noon meeting after lunch.
Before closing, they have another team meeting...
Thanks for this video
You are most welcome!
Thanks Gary. Another great video helping with my learning of all three 'kanban's, and an excuse for me to pull out my old Lego. The translation, from Japanese to English, for kanban is 'visual card/thing', so how did it end up being used for the framework and the principles? I think these de-value the first meaning. Try this test: "The Kanban Team moves the kanban across the kanban board, using kanban principles." The reason my dev team think I have lost my mind.
I have to agree with you. I do wish "Kanban-the-Agile-framework" was called something else. Not least because many Kanban-the-Agile-framework implementations have precious little "proper" (signal/sign, principles) kanban in them.
Just found this channel looking to prep for my PSK! Subbed :D I would think a benefit of specialisation is that the work can be done quickly (increasing throughput) as it is the expert performing the work, the downside could be a single point of failure should the expert get hit by the famous "lottery bus"...
Welcome!
Yes, you're right about throughput... and the single point of failure. Great stuff.
CaptainTiguan so to rephrase the downside point if the Coffee Man is sick/ill and had to leave the shop does Doctor Who know how to continue queue and use the machine?
Peter Taylor Exactly that. And reinforcing the point that “development teams” need to be cross functional, 3 or more in number and able to tackle the vertical slice! Any specialist advice should be taken when sprint planning and managers can be made aware of any upskilling required.
Love it
Delighted!
Coffee, Martini, perhaps a Sandwich or a demand signal for World Health Organization for contagious disease outbreaks, Gary what subject matter works best for you?
Who's fault is this...great question
Mr. I'm sharing on my Professional Linkedin network
I saw your post. I appreciate your taking the time to share to your network.
@@Developmentthatpays It has been a great pleasure Mr. I am not Native English speaking, but I understood better than many exhibitors speaking in Spanish, it must be because you British express everything more clearly than other Citizens of the World, it is also that his teaching method is very appropriate, to learn more agilely . Thanks
I don't understand what's the point in creating a maximum work in progress to three cups. It just seems like an artificial way of making it seem like there's less work. All your doing is turning paying customers away who would've else paid us and waited for their coffee to be made. So I'm Looking into the insight of the functional purpose of wip, thanks.
Great comment. I agree that I didn't make a strong case for the 3 coffee cup limit in this video; I'll do my best to do so in the next episode.
It is that if we allow a big queue of upstream/early stage work (eg order taken/empty coffee cup in this example) to build up because the downstream/next stage process is slower/not keeping up, then we are creating massive potential scrap - work upstream can continue to be built in an incorrect way without realising it (you only find out it is scrap when the downstream process tries to add to the next piece of value). The kanban prevents this and also visibly and physically makes you resolve the issue of an imbalanced system that one way or another will in itself create problems eg the imbalance causes the barrista to become massively pressurised as they are behind schedule so start rushing/cutting corners to catch-up, etc..
Perhaps the order taker can slow down the order taking process with pleasant chit-chat!
@@alexclark5809 - Thank you for bringing up re-work; although I like this coffee shop example, it's not the best to highlight the dangers/costs or rework.
@@michaelceraso6229 - Yes indeed!
This is awesome, I wish I was able to find you and your advice on Wisio.com!
Anarchists have long known it is the system that is to blame...!
Yes indeed!
so could we just use one sentence to summary the idea.
Do you have a good one?
@@Developmentthatpays sorry I don’t. I really appreciate this video but I want to know something short and clear
Hrm, I've had a though -- I know ... uncommon -- about the differences between Kanban within IT and Business, and I believe this may be something I've not appreciated in the past. Am I the only one here? *eek* If not, I'll stop chatting in this video. If so, let me know.
Please say more!
Can't obtain conceptual clarity from this video.Don't watch it.From India.
Sorry it didn't work for you. Could you recommend a better video?
@@zubairahsanimavoor7202 - agreed. Excellent video. 👍
Agree, this video was just a waste of my time. It's ridiculous to have "What's Kanban?" in title but not giving a definition for it in a video.
1:26 Masculine presenting, she/her pronouns.