Channel Title: Development That Pays Channel Description: Have you noticed the gap between what Agile PROMISES and what it DELIVERS? If so you're in the right place. Here you'll find the small - and not-so-small - things that make all the difference. So that you get stuff done, and have more fun doing it. Gary Straughan Founder of Development That Pays <video> What you taught me about Scrumban. (And Kanban.) Description: I asked you about Scrumban and your replies caught me by surprise. It is Scrumban that's confused... or is it me? = = = = = = = = = = = = New for 2024: my best-ever training: "How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout" → https://www.developmentthatpays.com/webinars/p-and-p?ref=yt = = = = = = = = = = = = Links: - The previous episode on Scrumban: https://www.youtube.com/watch?v=cFZDklA_ryQ&list=PLngnoZX8cAn8JwUdl3tfbIeB-VBZKqDGu - The LinkedIn post on Scrumban: https://www.linkedin.com/posts/garystraughan_scrumban-scrum-kanban-activity-7079821288302620673-YlVG?utm_source=share A huge THANK YOU to everyone who took the time to reply: you made this episode possible. ------------------- 157. What you taught me about Scrumban. (And Kanban.) #scrumban # scrum #DevelopmentThatPays I asked you for your thoughts on Scrumban and you responded in some numbers. I also got more than I bargained for. I've been getting something very wrong and it's time to come clean about it. Welcome back to the shed at the bottom of the garden. You know I had a comment not too long ago casting doubt on whether I really am in a shed at the bottom of the garden. So I think we need to put that one to rest and take this thing outside. Yes, it is a shed. Yes, it is at the bottom of the garden. You're not seeing it at it at its best: that's undercoat; I need to get a top coat on. That's on my Kanban board. But to business! Let's get straight into some of your many many comments. Here's one that I liked: "Dear Gary, I followed your channel for a while and it become quite a fan of Scrumban (excellent!) So now I'm scared... but always excited to see what insights you have to share". Yes, I do have some new insights. And the person who sent me this email is probably not the one that should be scared because, as you'll see, it's more me that became scared the more that I went into the comments. And to foreshadow that a little bit I had another email (I think it was an email - I'm not sure) saying that - in quotes - "If you tell me you're doing Kanban I also have a good idea of what you're doing". I think that was a quote - that was a quote - from me from my previous video all about Scrumban where I talked about how I thought it had an identity crisis and this person has basically said, "The Kanban bit: are you sure " He actually says "Do you think so " Yeah, we'll come back to that because that's quite key to some new realizations that I've been having. As I said, we'll get to that in due course. I sent out an email. I sent out some various quick questions on various places: I guess there was the video itself, all the comments that came into that. I also sent an email to my whole list saying if you have any thoughts on Scrumban please let me know. And last but by no means at least, LinkedIn. I also put a post on LinkedIn asking for feedback and I got plenty. But let's start with a real simple one: "Scrumban isn't that a cross between Agile Scrum and Kanban I think I've heard of it. But other than that I don't really have a strong opinion on the matter." Okay. The one that really made me smile was from Krishna on LinkedIn where he just says "Scrumban the agile turducken." And he provided a nice little picture of that dish - I'll put it up on the screen. And Krishna, you got me. I went looking for the etymology of that word expecting to find it was German or perhaps East European. It's not. It's just the words chicken turkey and duck. Not in that order, is it No: turkey, duck and chicken squashed together. A portmanteau word. I've tried to group these. I've tried to put some structure to it. That's not always easy to do. I had many people saying, well, expressing concern about "this Scrumban thing". Here's a good example of that: "I think many people who want to implement Scrumban don't always have the best intentions. They want some sort of easy watered-down version of Scrum. So really they want ScrumBUT rather than ScrumBAN. So it's Scrum but we're not doing the things that we don't like doing." Yeah, and I think in my in the previous video I'd expressed that very sentiment. This is a good one, also on an email. (By the way, when it's an email I'm not going to mention people's names. When it's LinkedIn I may mention people's names.) This is a good one: "Generally when a team tells me they're using Scrumban, it's another way of saying 'We do Sprints. We don't meet Sprint commitments. We can't make commitments. We pick the parts of Scrum and Kanban we want to do. We get all worked up done so don't bug us'". Yeah. The next series and Malcolm Lisle. Malcolm sent me an email but he also sent https://www.youtube.com/watch?v=17pYBpCjRcM&list=PLngnoZX8cAn8JwUdl3tfbIeB-VBZKqDGu </video> <video> How to give your Agile teams what they need so that you get what you want Description: Managers and Leaders - this one's for you! AUDIO STARTS AT 1:57. Jump on a Zoom call with me: https://tidycal.com/developmentthatpays/lets-talk-live ------ </video> <video> The Top Agile Channels - #2 Will Shock You! Description: We're counting down the top Agile Channels (on YouTube) by subscriber count. = = = = = = = = = = = = New for 2024: my best-ever training: "How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout" → https://www.developmentthatpays.com/webinars/p-and-p?ref=yt = = = = = = = = = = = = LINKS 1 - Development That Pays - https://www.youtube.com/@Developmentthatpays 2 - Agil Es - por Cris Rua - https://www.youtube.com/@AgilEsPorCrisRua 3 - Agile Training Videos - https://www.youtube.com/@AgileTrainingVideos 4 - Scrum Org. - https://www.youtube.com/@ScrumOrg 5 - Mark Shead - https://www.youtube.com/@MarkShead 6 - The Agile Digest - https://www.youtube.com/@AgileDigest 7 - Scrum Life - https://www.youtube.com/@ScrumLife 8 - La Minute Agile - https://www.youtube.com/@LaMinuteAgile 9 - BeingAgile Consulting - https://www.youtube.com/@BeingAgile_Consulting 10 - Mountain Goat Software - https://www.youtube.com/@MountainGoatSoftware Subscriber counts as of 2 April 2023. 0:00 - Intro 0:32 - 10 - Mountain Goat Software 0:54 - 9 - BeingAgile Consulting 1:09 - !!! RULES !!! 1:57 - 8 - La Minute Agile 2:21 - 7 - Scrum Life 2:41 - 6 - The Agile Digest 2:55 - !!! DISCLAIMER !!! 4:07 - 5 - Mark Shead 4:20 - 4 - Scrum Org. 4:36 - 3 - Agile Training Videos 4:49 - 2 - Agil Es - por Cris Rua 5:37 - 1 - Development That Pays 5:48 - Epilogue ------------------- 154. The Top Agile Channels - #2 Will Shock You! ##youtube #DevelopmentThatPays Years ago, I saw Danny Boyle being interviewed about his latest movie, "Sunshine." The movie was just about to be released and I was shocked to hear him say, and this was right at the beginning of the interview that everybody dies. So I'm gonna take a leaf out of the great man's book and giveaway the ending of this mini movie. This channel, the one you're watching right now, takes the number one slot, although that position comes with a number of caveats. We'll get to those in due course. But first of all, let's get started at number 10 with around 18,000 subscribers, Mountain Goat Software, a very recognizable brand. I'd heard of Mountain Goat before I'd heard of scrum and Mike Cohn is about as close as we get to a celebrity here in our agile world. By the way, you'll find links to this and every channel featured in the description below. (screen twinkling) At number nine with nearly 21,000 subscribers, BeingAgile Consulting. BeingAgile is based in the Minneapolis-Saint Paul's area. And Karen Fomafung is your agile evangelist. (screen twinkling) I think I forgot to say hello. Sorry about that. My name is Gary. Thank you very much for joining me here in the shed at the bottom of the garden. As you figured out by now, we're counting down by subscriber account. That was the easy bit. That's nice and objective, much more subjective was figuring out what makes an agile channel. Now, I took the view that one video does not an Agile channel make. So I've only included a channel if most of the videos on that channel were on agile subjects. I think that's logical. I hope that makes sense. Another decision I had to make was whether to include videos and channels that were not in English and I thought, why not Let's do that. (screen twinkling) At number eight, with over 22,000 subscribers, the first of two French-based French language channels, La Minute Agile. Luckily, I have a bit of French, so I can tell you that that means The Agile Minute. My French teacher would be so proud. Judicaël Paquet has produced an impressive 250 plus videos over just a three-year period. (screen twinkling) And number seven, with just over 30,000 subscribers, we stay in France for the only double act in the list. Scrum Life. I hope I'm pronouncing that correctly. Jean-Pierre Lambert and Constantin Guay have also been busy. period is no mean feat. (screen twinkling) At number six with nearly we traveled to India for the Agile Digest. Niladri covers agile and related topics, including Jira and agile transformation. (screen twinkling) Halfway there and as good a time as any for a quick disclaimer. Putting together this list turned out to be way more difficult than I had anticipated. Although YouTube search is very good, very good indeed, its search for channels is much less sophisticated. What I ended up having to do was search for agile videos and then trace them back to their channel. So that's one reason why this list may well be incomplete. So if you've spotted a channel that you think should have been on this list, please let me know in them there comments below. Another reason why it might be incomplete is that Google and YouTube both know that I speak English, so the chances ar https://www.youtube.com/watch?v=88ep-BiC95Q </video> <video> Live Training: "Discover The 7 Surprising Secret Steps That Will Transform Your Scrum Team" - Part 3 Description: Doors are OPEN for "The Scrumban Blueprint Transformation Experience": - https://developmentthatpays.thrivecart.com/the-scrumban-transformation/?ref=yt Missed a session? Catch up here: - Part 1: https://www.youtube.com/watch?v=q7Ap50pvFoo&t=380s - Part 2: https://youtu.be/u0TAFmlvkzE?t=212 </video> <video> Live Training: The Small Things That Make All The Difference For Your Agile Teams Description: "I just watched your latest webinar. When I loaded it up, I baulked at the hour+ timeframe. Then suddenly it was at minute 23, then 49, and I was madly taking notes and screenshots!" *** Click here to book your slot to talk about your situation: https://tidycal.com/developmentthatpays/lets-talk-live *** Join me as I reveal the small - often SURPRISING - things that make all the difference for Agile teams. All the difference in terms of: - Getting stuff done (Productivity) - Getting stuff done on time (Predictability) - And having fun doing it Gary Founder of Development That Pays ------ The results of the poll were as follows: - 3 - In a team / perfectly formed - 8 - In a team / not perfectly formed - 4 - Management / perfectly formed - 8 - Management / not perfectly formed </video> <video> Will the real Scrumban please stand up Description: I've been something of an advocate for Scrumban. But I'm the first to admit that it has a problem: it suffers from an identity crisis. = = = = = = = = = = = = New for 2024: my best-ever training: "How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout" → https://www.developmentthatpays.com/webinars/p-and-p?ref=yt = = = = = = = = = = = = Let's talk about it. ------------------- 156. Will the real Scrumban please stand up #scrumban #DevelopmentThatPays if you tell me that you're doing scrum I have a good idea what you're doing if you tell me you're doing kanban I also have a good idea what you're doing but if you tell me that you're doing scrumbine my first thought is oh oh welcome to development that pays my name is Gary Strawn and I have been something of an advocate for this thing scrum band at least one particular definition of scrum band you see and I suppose therein lies the problem there are at least two scrum bands scrumban the original and scrumban the young Pretender the original the OG was devised by Corey ladas who coined the term and quite literally wrote the book this is scrumban the pathway dare I say it the methodology specifically designed for scrum teams who want to transition to kanban this is the version that I've been an advocate for if you've seen me talk about scrum bum before you will have seen me talking about this particular pathway but there's a new kid in town the young Pretender scrumban the agile framework not just an agile framework but a hybrid agile framework incorporating we're told the very best of scrum and kanban and I have to say if you go Googling for scrumban it's this young Pretender that comes up again and again yes there are references here to the OG but it seems as far as the interweb is concerned the war is over and the young Pretender has won and I'm not sure that that is a good thing for a couple of reasons for one thing I have a theory that the very name scrum ban might be part of the problem if you're hearing about it for the first time here today I wonder if you're already imagining how you might mix and match drop a bit of scrum here add in a bit of kanban there and see what happens and I guess really what my concern is that many people are rolling their very own agile framework perhaps quite randomly and giving it the label scrumban when what it really is is Scrum minus the bits we don't like or find to be inconvenient I wonder if you uh know anyone who might have been guilty of this if you're watching this I'm sure I don't have to tell you don't know every combination of scrum and kanban is going to be valid especially not if we're attempting to create a framework so this young Pretender is going to have to be a specific combination we're going to need a scrum band guide and the great news is I found one the not so good news is I then found another one seems like there are lots of guides definitive guides ultimate guides for how to do scrumban and I wasn't really able to find very much commonality between them than I have to confess that I got discouraged packed up and went home but if you didn't if you have gone through that process of finding out about scromban and found a good source and ideally a source that you then went and implemented I really love to hear from you let me know in them their comments below but as I said my conclusion was this is a big mess I give up but I may have been a little Hasty take a look at this this is from get clockwise.com and it reads scrum band was originally intended to help teams transition from scrum to kanban as we have talked about however many teams found at the midpoint was actually a great place to stay for that reason you'll find nuances in the way that different companies Implement scrumban interesting perhaps what I was looking at was a feature and not a bug scrumban as a collection of agile Frameworks and I guess it makes sense after all the OG the original scrum band was indeed a pathway starting at scrum ending at kanban with presumably scrumban in between multiple scrum bands in between that being the case you'd think we'd be able to find them right here in this book except they're not there this I'm afraid is a lie yes the book starts with scrum yes there are multiple stages along the way but most of those stages are about adding kanban elements to scrum without taking anything away this isn't scrum but this is Scrum and scrum and those kanban elements now what's another name for scrum and bearing in mind the scrum is a Nigel framework that's the important word it's a framework so that we're at Liberty to add things to it meaning that scrum and is the same as scrum me https://www.youtube.com/watch?v=cFZDklA_ryQ&list=PLngnoZX8cAn8JwUdl3tfbIeB-VBZKqDGu </video> <video> Blockers: 5 ways to handle them on an Agile Board Description: </video> <video> 13 ways to BREAK Scrum. (Easier than you think.) Description: None of the "breakers" are picky: you'll find most of them in the Table of Contents of the Scrum Guide. = = = = = = = = = = = = New for 2024: my best-ever training: "How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout" → https://www.developmentthatpays.com/webinars/p-and-p?ref=yt = = = = = = = = = = = = Check out the full Scrum Guide here: https://scrumguides.org/ ------------------- 158. 13 ways to BREAK Scrum. (Easier than you think.) #scrum # scrumguide #DevelopmentThatPays Scrum, as I'm sure you know, is a framework. And because it's a framework we can adapt it to our needs. It's actually highly adaptable. As the Scrum guide says, it "functions well as a container for other techniques, methodologies and practices." We can add, but we can't take away. Welcome to Development That Pays, the number one agile channel on YouTube. My name is Gary Straughan and I have a question for you. Did you by any chance do French at school I did, and I was particularly bad at it. And the thing I was most bad at was dictation. I found the marking process, you know that thing where you swap books and mark each other's work Yeah, I found that rather humiliating. You know the way it works, 10 points to start with. Lose a mark for every big mistake, a half point knocked off for a misplaced accent or a mixed up gender. I can tell you that a mixed up accent was the least of my problems. By the end of the first sentence I was inevitably every time down to null points. But I'm sure you'll do much better as we play a similar game with Scrum. You're gonna start with 10 points and knock one off for every time your version of Scrum differs from the Scrum guide. And don't worry, there'll be no pickiness on my part. We're gonna keep things very high level and there'll be no judgment either. I can tell you that most of the Scrum teams I've been a part of would've struggled to hold on to all 10 points, but you just might. Let's take a look. Over to the Scrum guide and I think we're gonna find most of what we need right here in the table of contents, specifically these four sections. Scrum values, Scrum team, Scrum events, and Scrum artifacts. Let's get things off to a gentle start with a look at those values. Successful use of Scrum depends on people becoming more proficient in living five values. Commitment, focus, openness, respect and courage. This section is a relatively recent addition to the Scrum guide. The authors must have thought long and hard before including it, and for that reason I think we need to take it seriously. These values are not to be considered optional. Having said that, it's a tricky one to score for the purposes of our game here today. So unless you know your team is entirely lacking in one or more of the above, then I'm not gonna dock any marks. I'm gonna move a swiftly on to talk about Scrum events. Yes, you're right. Scrum team is the next one on the list but I'm gonna save that one for later. Your points will thank me. The Scrum events formally known as ceremonies are, the sprint, sprint planning, daily Scrum, sprint review and sprint retrospective. The sprint for me, perhaps for everyone is the defining feature of Scrum. So if you're doing Scrum I'm pretty sure that you're working in sprints. The guide describes a sprint as a fixed length event of one month or less. So lose a point here only if your sprint is longer than one month. And lose a point also if you flex the duration. Onto sprint planning. And again, if you're working in sprints I'm sure that you plan each of those sprints. So whereas I could get a little bit picky here I'm gonna move right along to the event that shares its name with the framework. I'm talking of course about the daily Scrum, also known as the daily standup. The Daily Scrum is a 15-minute event for the developers of the Scrum team. Drop a point if you don't do daily Scrum. Also drop a point if you don't do it every day. Now don't give me a hard time about this. After all, it's right there in the name. How are your points doing I thought I'd just ask before we get to the next two events. No reason. The purpose of the sprint review is to inspect the outcome of the sprint and determine future adaptations. Drop the point here if you don't do sprint reviews and yeah, drop a point here if you don't do a sprint review every sprint. The purpose of the sprint retrospective is to plan ways to increase quality and effectiveness. Drop a point if you don't do them. Also drop a point if you don't do them every single sprint. Did you just drop a point Nevermind, I'm sure things will improve as we move on to the next section, Scrum artifacts of which th https://www.youtube.com/watch?v=F6jXfhmAaFE&list=PLngnoZX8cAn-a1tR12eN2F0rdJW0003ry </video> <video> Why is Agile so... ANNOYING? Description: Cast your mind back to your first Agile team. What was the first thing that struck you? The first ANNOYING thing? = = = = = = = = = = = = New for 2024: my best-ever training: "How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout" → https://www.developmentthatpays.com/webinars/p-and-p?ref=yt = = = = = = = = = = = = That's the question I'm asking in today's brand-new episode. Enjoy! ------------------- 155. Why is Agile so... ANNOYING? # #DevelopmentThatPays if pressed I could probably come up with a list of things about agile that are not ideal today I'm going to talk about just one of those and then I want to hear from you hi my name is Gary welcome back to the shed at the bottom of the garden and welcome to development that pays the channel where we actually what is it that we do it's a question I've been musing about over the last few weeks and at the beginning of this week I put up a poll to ask what you thought might be a good tagline for development that pays the options were your agile Survival Guide getting stuff done without losing your mind agile for me Immortals and agile gain without the pain which one I wonder would you have chosen here are the results have to say I'm pretty pleased with how that turned out and interesting isn't it that the top two results both have some element of pain annoyance frustration built into them and it had me thinking back to my first encounter with agile and the first time I experienced some frustration if you've been with me for a while you'll know that I was dropped into an agile team at the BBC a team that was doing scrum although I hadn't heard of that term just yet and my initial impression was one of well Fascination I'd never seen anything like it the daily stand-ups the planning meetings retrospectives think we even had beer from time to time so yeah initially it was all fascinating but that wore off quite quickly and I I shared the frustration that I think many people do expect maybe especially on the coding side I don't know maybe with other roles as well that felt like my time might be better spent doing more coding and doing a little less of these various meetings ceremonies I think they were called back then if you know the full story you'll know that the team split in two one team wanted to do kanban one stage doing scrum and that was when I started to take notice of what both teams were doing to compare and contrast and eventually get to a point where I understood why we would spend time at the beginning of the week planning I understood why we would spend some time at the end of a Sprint doing a retrospective doing a Sprint review the pieces started to fall into place in my mind and that's when I discovered my second frustration and that was when I started to understand I wanted to help other people understand so that they would be less frustrated about some of the stuff they were doing and I found that I was very poor at communicating that long story short that's the origin of development that pays it was me getting my thoughts together on these various things these crazy things that were happening in agile and putting them down in a coherent way that would hopefully be useful to explain to others so that's two or one depending on how you look at it pain points from me but I'm interested to hear from you especially your first one so can you remember back to your very first or second maybe experience with agile and what it was that first annoyed you frustrated you drove you crazy I hope that never happened to you but if it did I'd really love to hear about it let me know in the comments and as you've continued your agile journey I wonder if that pain has been replaced by a different pain perhaps something even more acute if so I'd love to hear about it let me know and then their comments below and I look forward to seeing you next time https://www.youtube.com/watch?v=ga4GCy9sHCU&list=PLngnoZX8cAn-xfi24VnXN43gFHER5xCGM </video> <video> Scrum: How is fixed is your Sprint Backlog? Description: </video> <video> Best Agile decision-making tool is not an estimate Description: The most powerful decision-making tool in your Agile toolbox… is also the most under-used. Which is weird, because outside of Agile, it’s used all the time. = = = = = = = = = = = = New for 2024: my best-ever training: "How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout" → https://www.developmentthatpays.com/webinars/p-and-p?ref=yt = = = = = = = = = = = = ------------------- 159. Best Agile decision-making tool is not an estimate #agileforecasting #DevelopmentThatPays Let’s start… with this guy: my friendly neighbourhood builder. He - together with his small team - was responsible for swapping these rotten old doors For this single aluminium door. But before he did any of that, he provided me with an “estimate”. The estimate - let’s call it the builder’s estimate - answered two questions: When will it be ready And (for me, the far more important question) What will it cost It’s worth taking a moment to think about the “margin of error” here If you’ve ever dealt with builders, you’ll already know that it’s going to take longer and it’s going to cost more. And that’s expected. After all, it was an estimate, rather than a quote. But how much more The pain can sometimes be hidden in percentages, so let’s talk cold hard cash. Say my builders estimate for this project was £10,000. If the final bill comes in at £11,000 (10%)… I’d be okay with that. £12,000 (10%) or more, and my builder goes from “friendly neighbourhood” to “neighbourhood” Margin of error-wise, there’s an unspoken agreement that if things go smoothly the final bill will be within 10–20% of the estimate. And that NARROW margin is what makes the builders estimate useful for decision-making. Specifically, the decision on whether to go ahead with the project in the first place. One more thing before we move on. Imagine the bill came in at £16,250. - a full 62.5% greater than the original estimate. That’s an oddly specifc number! Yes, isn’t it. I’d be okay with that too, as long as it reflected an AGREED change to the original spec. That’s another property (!) of a builders estimate: it gets adjusted in light of new information. Forecast Question for you: what’s our AGILE equivalent of the “builder’s estimate It’s not the estimate. Same name. Different animal. A Story Point estimate: Applies to a single work item, rather than to a “body of work” Tends not to updated in the light of new information Answers a different question // “relative complexity” And does so with a huge margin of error of ~62.5% or thereabouts. // I could do extra voice-over later. No, the equivalent we’re looking for is the forecast. If I FORECAST that a certain piece of functionality will be ready in 10 weeks, I’ve answered the question When will it be ready I’ve also answered the question What will it cost At least I have for a software development team, where the majority of the cost is in paying the team keeping the lights on. Put another way, if I know how long it will take, I know how much it will cost. Great for decision-making - providing that the margin of error is reasonable. If I give you a forecast of 10 weeks, I’m sure wouldn’t be surprised if things run over by a week (10%) But you’d be less happy overrun was two-weeks or more (20%) Interesting, isn’t it, that we AGAIN have an unspoken agreement of a margin of error in the range of 10–20% And, yes, it’s achievable. Good enough for decision-making in my book. Not only for the go/no go decision, but for coordination with other activities. But the reality is that few Agile teams forecast at all. Either because they think it’s “not a thing”. Or because they think that it requires too much work. https://www.youtube.com/watch?v=j49vtI0yWRw&list=PLngnoZX8cAn_dRhRh9Un8fGD7Mc04Lnu_ </video> <video> How to Supercharge your Agile Board (Kanban Board) Description: I'm sharing EVERYTHING I know about Agile Boards... in the hope that YOU will share with me. I look forward to talking to you in the comments. 👍 = = = = = = = = = = = = New for 2024: my best-ever training: "How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout" → https://www.developmentthatpays.com/webinars/p-and-p?ref=yt = = = = = = = = = = = = Notes: - There's a mistake at 14:24 - the title should say "Driving a Wedge?" - Please don't leave without leaving a comment - I want your tips and tricks! 00:00 Intro 01:12 To Do, Doing, Done 2:50 Triggering 4:49 Release me 6:50 Ageism 7:36 WIP Limits 9:43 More columns 14:27 Driving a wedge? 19:53 Blocked items 22:30 Swim Lanes 24:10 Not fair! ------------------- 160. How to Supercharge your Agile Board (Kanban Board) #agile #scrum #kanban #DevelopmentThatPays Kanban boards, Agile boards Scrum boards - whatever you call them we're going deep on them I'm talking column naming process columns buffer colums Swim Lanes blocked items WIP limits card aging everything from the basics to some rather nifty tips and tricks Welcome back to the shed at the bottom of the garden where we are for the very first time attempting a fancy 2 camera setup. And no: what's coming is not a rant about physical boards versus Agile boards. Most of what I'm going to be talking about today can be done on both but I will be highlighting things that can only be done on a physical board and one or two things that can only be done on an electronic board That said what are we looking at here well we're looking at a Kanban board that's probably the most correct word for it name for it Agile board I think is probably become quite common Scrum board as as well often used by Scrum teams surprising that whatever you call it I would recommend it for any Agile team regardless of framework or methodology. Three columns - not three Swim Lanes by the way: I'll say more about Swim Lanes later. Three columns To Do Doing and Done. This is the only column where work gets done - you could call that an active column I call it a process column. I'm not even sure that's the right term if you know of if you know of the correct or better term please let me know in the comments The board of course is for tracking work the very first board I had any dealings with was was one very much like this it was using a whiteboard with drawn on columns and index cards to track individual backlog items across the board aided and a beted of course by a Blog of BluTak other brands available the second board I had dealings with was printed on a big sheet of paper with columns just wide enough for a single PostIt and this is how the board might look for a Scrum team if this was right at the beginning of the Sprint the items here are essentially the Sprint Backlog That's of course not the case for Kanban more on that in a moment when an item is picked up it's moved into this column to indicate that it's now being actively worked on and it's at that point and know earlier that this item should be assigned to a person as time goes on items get pulled in from to-do and eventually items may get all the way across to the done column and by the time if this is again if this is still the Scrum team by the time we get into the middle of the Sprint that the board looks pretty much as it would for a Kanban team Going back to the to-do column as I said Scrum teams have a Sprint they have Sprint planning they have a way of generating work for this column. In Kanban things are a little different in Kanban the the work pretty much drives everything and we can enable that with another line on this [Music] board this in Kanban is called called a trigger point. It's very much like a reorder point that supermarkets and such like will use to let them know that they're running short on a particular item and that they should go on and order more stock and that's exactly how it works on the board in this position there were three items still left in to do well nothing to do at the moment but when this item gets picked up and now these two items move move up above this trigger point that's the time to call a meeting and and typically it takes a while to get the meeting together to run the meeting to the result of which will be more items for the to-do column and the idea being is that if this is the state when the meeting is called there's enough work to carry on with if it takes say a day or perhaps ABS two days to get that meeting organized so maybe this one gets picked up in the meantime this one gets Al also gets picked up and then finally the result of that planning meeting would be https://www.youtube.com/watch?v=O0BnP45op0E&list=PLngnoZX8cAn9ybPBWdlydv7AaqdifaE27 </video> <video> Live Training: "Discover The 7 Surprising Secret Steps That Will Transform Your Scrum Team" Description: Doors are OPEN for "The Scrumban Blueprint Transformation Experience": - https://developmentthatpays.thrivecart.com/the-scrumban-transformation/?ref=yt Don't miss Part 2: - Part 2: https://youtu.be/u0TAFmlvkzE?t=212 </video> <video> Live Training: "Discover The 7 Surprising Secret Steps That Will Transform Your Scrum Team" - Part 2 Description: Doors are OPEN for "The Scrumban Blueprint Transformation Experience": - https://developmentthatpays.thrivecart.com/the-scrumban-transformation/?ref=yt Missed a session? Catch up here: - Part 1: https://www.youtube.com/watch?v=q7Ap50pvFoo&t=380s </video> <video> Top 10 Agile Channels 2023 Description: These are the BIGGEST Agile Channels on the planet: 1 - Development That Pays - https://www.youtube.com/@Developmentthatpays 2 - Agil Es - por Cris Rua - https://www.youtube.com/@AgilEsPorCrisRua 3 - Agile Training Videos - https://www.youtube.com/@AgileTrainingVideos 4 - Scrum Org. - https://www.youtube.com/@ScrumOrg 5 - Mark Shead - https://www.youtube.com/@MarkShead 6 - The Agile Digest - https://www.youtube.com/@AgileDigest 7 - Scrum Life - https://www.youtube.com/@ScrumLife 8 - La Minute Agile - https://www.youtube.com/@LaMinuteAgile 9 - BeingAgile Consulting - https://www.youtube.com/@BeingAgile_Consulting 10 - Mountain Goat Software - https://www.youtube.com/@MountainGoatSoftware </video>

Contacts and Links

Description

Have you noticed the gap between what Agile PROMISES and what it DELIVERS?

If so you're in the right place.

Here you'll find the small - and not-so-small - things that make all the difference.

So that you get stuff done, and have more fun doing it.


Gary Straughan
Founder of Development That Pays

Videos from channel