What is Kanban? From Coffee Shop to Kanban Card
Вставка
- Опубліковано 23 вер 2024
- Can we take what we learned in the coffee shop and apply it to our Agile/Kanban boards? Yes, we can!
= = = = = = = = = = = =
New for 2024: my best-ever training:
"How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout"
→ www.developmen...
= = = = = = = = = = = =
-------------------
142. What is Kanban? From Coffee Shop to Kanban Card
#kanban #agile #DevelopmentThatPays
At the beginning of the previous episode Our hero - the barista - was doing it all: Taking orders, making coffee… and delivering it to the customer. Let’s get that up on a board! Hmmm. a bit minimal minimal. Is there anything we can do to flesh it out a bit We could add a “Done” column. And to balance things out, we could add a “To Do” column. Which actually makes a lot of sense, especially if we consider that our coffee shop “process” extends to the front door. The coffee shop’s “to do” list is this queue - I’ll say more about that in a second. Three columns:Two - I’m going to make them grey- where things kinda hang around. And one where we - we of the coffee shop OR development team - get things done. Where we ADD VALUE. Did Dr Who feature in the first episode. Or was that a different Time and Relative Dimension in Space Strangely he did feature. In the role of an assistant of sorts. He arrived… of the blue at the point where we chose to SPECIALISE. Dr Who taking Orders; the barista making and delivering the coffee. Lets get that reflected on the board: Hmm. Now I look at this, I’m not sure that “Deliver Coffee” deserves a separate column. But I do think it’s constitutes a rather lovely DoD for Make Coffee. The Make Coffee step is complete, when the coffee is delivered to the customer We tend not to put people and coffee cups on our boards so I’m going to swap them for PostIt notes. Did I just pull a fast one The coffee cups - with their checkboxes - are definitely kanbans. But what about the people in the queue One way we could square the circle would be to change the coffee shop: to have people pick up a cofee cup as they arrive. (are there coffee shops that work this way Problably a hygene issue,.) But I don’t think we need to: All we need to do is realise that the people in the queue... are kanbans. Think about it: they carry information about coffee selections… even though we can’t see it yet. It’s also worth saying that the queue - or rather this To DO column - Is not only a product backlog. It’s probably the best backlog in the world. A backlog that Heiniken might have made. Here’s why: It’s ORDERED It’s self-limiting - when the queue extends out of the door, no one will join it And it’s dynamic - it will respond (by either growing or shrinking) to our (speed of) actions. Even the coffee selections are dynamic! It’s always up to date… never stale. And all without any effort on our part.
• What is Kanban? From C...
I am just learning some of this stuff. Gary presents Kanban, Agile, Scrum better than anything else I've found, even compared to some of the paid apps. Great teacher.
Paul - That's very nice of you to say so. Thank you!
So Gary has in fact made more sense for me from my reading on books about these topics so well done! Trouble with the board is that various family members are not visually inclined (prefers talking or discussion verbally) so I’m the only one who wants a white board. Hmm how to reconcile?
I've had the same experience: somehow - when it comes to your own family - the laws of nature go out the window.
I had to chuckle about the remark of people being added to the "To Do"-column. I have an ambiguous mind...
I love your way of explaining. I like listening to your voice. Keep them coming.
Oh yes! I hadn't thought of it that way 😊
Really glad you liked it.
It’s taken months of bungee cording back and forth to land on the board my Kanban team currently has. After a LOT of evolutionary change, we landed on 10 very useful, universally understood (an important detail) columns. To Do | selected | PREP | ready | COLLABORATE | agreed | DOCUMENT | drafted | APPROVE | Done.
The all caps are the work columns, the lower case are the wait columns. There is a SUPER long story on how we landed on the titles, but given the exact same number of columns it didn’t work for weeks and weeks, until these titles almost magically snapped it into function.
Fantastic! Love that your work columns are all imperatives ("Collaborate!"). As for the wait columns, are they "owned"? (Eg, by the preceding work column)
PS - If you have time, it would be great to hear the longer story :)
Dear Gary. You are a brilliant Teacher (Guru). I will be learning a lot from you. 🙏🏻
I was an agile coach for a kanban team, and the board I made was more like the second one, where the work from Order-taker went into a queue for Coffee-maker to pull from.
Another great video, Gary! You're quite right, it's not a coffee shop without ambient music, good catch on that!
Jon - the music is everything! 😂
Excellent as always.. just added to the "Help" project in our company kanboard
Excellent!
Well done, Gary. This video is perfect to understand why this method was developed. Your case Coffee Shop is so great for a easy example to explain the philosophie.
I am using a scrumban board (incl. WIP-Levels) similiar to yours and develope the team since 4 weeks in the intuitive use of it. I will show them this video ! Thanks for that help.
Very curious how you continue ...
Really glad you liked it! I hope the Part 3 will also be helpful 👍
Great video Gary! The concepts, animation, and thought process we all go through - we all have a shared experience. To answer your question, my prior customers enjoyed the 3 column board while we expanded it to > 3 columns for the development teams.
Really glad you liked it! (It took rather a long time to put together!)
I really like this video, it was amazing clear for me when you show in the physical world how is to push tasks to someone else, it's like the rude movement of pushing to someone's face with a cup
excellent - great work. to the point, inspiring, clear, entertaining. thanks a lot!
Delighted that you liked it!
Love the editing on this one Gary, keep up the great content!
Thank you! The episode is - I hope! - even better. Look out for it tomorrow.
wow Doctor who, great British series You are a Great Master, MASTER with capital letters
you forgot the coffee shop music at the 10:00 min mark!! Funny as Gary...love it. Appreciate all the extra animations too!!!
It was there, and then I took it out: I felt it was time to break free of the coffee shop. Maybe I should have added different - development-specific - music?
Special thanks for coffee shop music 😁 Fine selection, as always. The queue as a product backlog - interesting idea. Would happy to hear more about it. Great episode!👍
Yes! The coffee shop music was your suggestion! It made all the difference - thank you!
@@Developmentthatpays I know and feel satisfied with it😋
GREAT GREAT SITE MR.
I have been a professional programmer but once I took a management role due to a silly constraint that the company had, which is omitted here.
I did my research, in which this channel largely helped. I went full-on. My team's board had from todo to necessary tasks to done, with doing/done sub-columns if needed, done on Jira, mind you. I explained to the members why we needed this board and system at all, what are the push and the pull and why are they needed here. All I got was "I don't wannaaaa". I felt like a teacher leading a school project, lower graders at that. In the end, I quit the company not directly because of those developers, but rather the upper management being ok with that attitude. Also I've decided that management is fun, but not for me, at least the baby-sitting part.
I feel your pain - having experienced some of what you described. My frustration in my "day job" agile teams led directly to me posting videos to UA-cam!
@@Developmentthatpays Thank you. I feel at ease knowing someone out there experienced the same thing. One thing that I harvested from that period, besides learning about agile methodology (reading up Pheonix Project/The Goal gave me valuable insight on what I am doing in the process of delivering a software product), is that now I know I want to work with people who want to make "better things". Whether certain things are good or bad is always debatable, but at least I want to talk it out and head somewhere, instead of doing things out of rote.
Great work Gary, keep it up :)
Great presentation - my previouus team's board is more like the second option but I have a new team and I'd like them to go Kanban - I love your explanation, and watching this is good timing to share with the team at the next retro.
Really glad you liked it! Hope the retro goes well.
Brilliant!!!
Thank you!
Mr. It is proven that we adults, by more technically and professionally prepared, to learn is easier playing, and lego is the best, I have experienced it training Engineers in PMI(R) management processes
Awesome demo! Just one bit of feedback- I noticed that the To Do column conveniently never 'overflowed.' I wish the coffee shop I visit always had less than 3 in line ahead of me. Yet in the case of the coffee shop the process lead time begins at customer arrival. I know you're just showing Kanban, but I do hope you will show the waste in the system, mostly in the form of Wait.
You raise excellent points! I'll address at least one (and hopefully both) in Part 3.
excellent video. keep it up.
Hi Gary, another nice episode, Thanks.
May I suggest to keep the grey color in the “Done” column (@12’) since it was your conversion to show that no extra value is added there?
And what about merging the “Make” and “Done” columns in a big “Make” process step with sub “Doing” and “Done” as you did for “Order”? In that way all process steps are setup the same way and the last one includes the overall done column.
Christian: Great catch: the "Done" column should indeed to be grey (from 11:21 onwards). Annoyed with myself! 😱
Like the idea of keeping things as consistent as possible... but I'm not sure I'm ready to mess with an agile stalwart: the "Done" column.
GREAT VIDEO GARY I LOVE DOCTOR WHO
Delighted! Which Doctor do you think the lego guy is?
@@Developmentthatpays Paul McGann? or could be an older looking Matt Smith
@@visualvirtue Glad you said Paul McGann: in the next episode, his sonic screwdriver makes an appearance...
@@Developmentthatpays Post notifications are on! I'm looking forward to seeing what happens!
@@visualvirtue Hope I haven't over-sold it!
Wonderful coffee shop analogy, thanks Gary! And I would like to ask how you consider task estimation in this context? Each coffee cup is deemed an explicit task that records the size, the name, the type of coffee, etc., whereas most tasks are not defined so clearly when initialising them on the board. And we know that Kanban does not support these estimation stuff like Scrum, so it seems that the coffee shop case does not reflect well from this perspective.
my board was more like the second one , great video by the way
Thank you!
Dude you are awesome
Thank you! Really glad you liked it!
more like right one
where is the link to part 3?
Here you go: ua-cam.com/video/LFYnkFq3ITE/v-deo.html&lc
Great episode, Gary!
But who's this "Dr. Who"? I'd rather call you "Dr. Queue", Gary! :))
Can I maybe see Dr. Who's possible foul again in slowmo? Not absolutely sure if it was really him pushing and not rather the Barista pulling knowing the other coffee would be "Done" in just a few seconds and he'd be able to handle that... maybe we should ask the video assistant referee here? ;)
I wonder if I could add a VAR for Part 3. It's the only way to know for sure!
Gary ❤️❤️❤️❤️
Too kind. Too kind.
Subscribed!
Great video that is definitely enriched with Dr. Who (or Dr. Queue). For some of the teams I've worked with we've used more columns like Requirements with a In Progress and Done sub-column and the same for Development and Testing. One question would be how the system would respond to a defect, perhaps the extra whip cream on the mochaccino didn't get added. Is there an expedited process for these situations?
Responding to a defect? Oh no! Don't say I have to do a FOURTH episode!!!
I just learned that we should avoid to be pushy. But still it´s a push from "order - doing" to "order - done" .....hmmmm.....kinda confused now......
Excellent point! It's not a push - stay with me here! - because it doesn't go anywhere. It's a change of state within a process, rather than a move (handoff) to another process. Does that make sense?