@HippocraticDev
"Why's this blocked?" "I'm waiting for so-and so to get back to me" "What can we do about that?" "I'll email him today" "Where's his office?" "Bangalore, India" "oh ok.... send him an email then I guess"
@rcronk
In my experience, Kanban works well for service-oriented teams like IT, or any team fixing an ongoing stream of bugs being found, or fires that need to be put out. Scrum works well for teams building features/stories as part of a product to be released. Many teams do both of these kinds of work and switch between them based on what's more efficient at the time. Kanban is useful for pre-emptive interruptions by fires. Scrum is better at keeping non-fires moving along without being starved by firefighting. Kanban is more tactical, scrum more strategic. A balance of both is a good thing. I didn't see this in the video so I figured I'd share.
@BolaAdesope
This is probably the most efficient way to drive home any concept. The theatric theme made it all fantastic. Cool stuff. Just FYI, your subscriber base just grew by one....
@milojeffrey6457
Development that Pays, Thank you for speaking slowly and clearly. Not all Youtube educators grasp that students hearing the information for the first time need it delivered slowly and clearly. As a Yank, I find your smashing British accent most enjoyable. Your videos are fantastic. Bravo!
@OmaticFever
Great explanation of the different Agile methods. I can see how Agile, done correctly, doesn't make you want to end your life. My company's digital transformation was done so horribly wrong. "Blocked" was code for "go to that department's VP and make the person that I think can solve my problem work on my problem until its resolved even if he has other priorities" and their were no WIP limits. I long to work at a company with better culture.
@christerpettersson7943
This video have transformed my view on agile. Three ongoing non-it projects on my workplace switched from Agile sprints (wouldn't call it Scrum), about five months ago, to Kanban, and the speed of all these projects have increased significantly. Thank you!
@eeyore345
This is the MOST entertaining video I have ever seen to explain this topic. Most of the videos/courses out there are so boring and dry, this video makes it sound like I am watching a Bond movie. :) I must admit that I shared some of the same hesitations like the storyteller when I first started Scrum. Not that I am entirely sold at all aspect of things, but now I see how I should look at things with a bit more positivity before rejecting them.
@lifesacardgame6454
Just found this. Made me laugh and cry in equal measure because this is where I'm at. Thank you for making me feel that I am not alone!
@crazydmd
Thank you for posting an informative video that addresses an important topic. We use Scrum but we also utilize the Kanban boards in Jira. At about 7:00 minutes, you attempt to draw a comparison between Team Scrum and Team Kanban with 95% time working vs. 100% time working, respectively, but one cannot compare these two percentages as quantitative measures since Team Scrum may be working more efficiently due to better task planning, as is the case in my experience working on both Scrum and Kanban-only teams. In Scrum, the whole team is involved in estimating the number of Fibonacci points to assign to a task and therefore a consensus-driven estimate is more accurate. I’d also like to point out the “gamification” of the Scrum process provides a daily reward for progress made on a given task. Deducting a few more points from a task occurs daily vs. a task in a Kanban that could take an hour or several days; you’re not "rewarded" as often. The point system in Scrum enables the Scrum master to visualize team progress for a Sprint with burndown charts, and act if the team is running behind. With Kanban, you can only measure progress by the number of tasks in the Completed bin and it's not as granular a measure of progress.
@kevinsusko8395
Thank you Gary ... very nice (and clear) description of Scrum vs Kanban. Coming from a client consulting view point, our "transition" from Scrum to Kanban was by accident (or need if you have your "lead" hat on) by keeping up with priority releases which never fit into the 2-week sprint idea. The "limited scope" of the DEV column is a what keeps the team sane but also allows a semi-structured view of what the next release will look like (quite scrum-like ... without the anticipation of Friday's meeting). Your video clearly shows that it's not a deviation from the structured Agile method (which sounds like an oxymoron) without cause but there is a way of keeping Kanban from becoming the Wild Wild West of releases. Keep the videos coming!
@alanhunt7082
I enjoyed the light and easy manner in which you defined the difference so people could readily understand without being to process-driven. It is enlightening to read different peoples current experience level and it's easy to see those who are still fighting the emotive struggle... My story will have to be short, but I recall a global telco when it started its transformation journey, we had multiple DevOps teams all offshore working to different sprint cycles, complicated by onshore program teams applying different sprint durations and just to add a little more fire to the story we had recently qualified CSM scrum masters i.e. (former project managers) drawing up classic DESIGN/BUILD/TEST MS schedules in the background, across 47 two week sprint iterations.. It was a wonderful experience because I believe you learn a lot more from what does not work, rather than those deliveries which perform like clockwork. :-) The scrum coaches could not resolve the issues!!
@brutusmaximumus
Back in the early 2000 or maybe 2001 I was tasked with creating a digital kanban workflow system for supply catalog digitization, multiple teams of people scanning, OCR'ing, categorizing, QA'ing, etc. paper catalogs into digital format. I'd never heard of kanban at the time, but one of the first things I learned and had to put in my solution was the concept of queue limits. Reading up on the history of kanban and its origin in Japanese manufacturing was the concept of eliminating bottle necks by stopping all upstream work until the bottle neck was relieved, once everything grinds to a halt and everyone is running around with their hair on fire it becomes super easy to go do what it takes to remove the bottle neck as opposed to letting it sit there and moving on to something else.
@ivan-parra
I've never commented on a youtube video before, but this video is great, and the Yoda "Deliver more often, you must" joke was hilarious
@bhaibhai2012
Quite interactive to inform about terms of Scrum vs Kanban..Usually we will prefer Scrum: when we have good number of stories well detailed and can start with them for couple of sprints, rest of stories still needs grooming..Also when we have to behave emperical approach in mind(considering previous sprint experience and improvise current sprint planning and progress as we do not overall vision on to reaching the closure of project)
@webanyware
Agile or Kanban, working on one task/story that reaches completion at a time is the way. Great video! Thanks
@kenechukwuujam1479
Thank you so much for this lesson. I was so captivated by it. So in summary, for Scrum and Kanban, let fools contend, whichever is properly done is the best option (apologies to Alexander Pope).
@taranouveau5454
Loving the voiceover. "No photographs exist from the time period..." V entertaining.
@idselseno2306
Haha! My freelance project is still on the level of 'Superficial' agile. All devs commit at least 20 hours a week and all work remotely. This has been really quite a challenge for the past months. This video really enlightens all! Keep up the golden content!
@tarvinder91
I knew nothing of these topics and after watching this video I have a lot of info in my head now. Thanks.
@Developmentthatpays