How to optimize your Agile Board (Kanban Board)

How to optimize your Agile Board (Kanban Board)

HomeDevelopment That PaysHow to optimize your Agile Board (Kanban Board)
How to optimize your Agile Board (Kanban Board)
ChannelPublish DateThumbnail & View CountDownload Video
Channel Avatar Development That Pays2024-02-14 14:00:18 Thumbnail
2,697 Views
I'm sharing EVERYTHING I know about Agile Boards… in the hopes that YOU will share it with me. I look forward to talking with you in the comments.

= = = = = = = = = = = =

New for 2024: my best training so far:
/"How your agile teams can achieve predictability and productivity WITHOUT burnout/"
→ https://www.developmentthatpays.com/webinars/p-and-p?ref=yt

= = = = = = = = = = = =

Remarks:

– There is a mistake at 14:24 – the title should read: /"Driving a Wedge?/"
– Please don't leave without leaving a comment – I want your tips and tricks!

00:00 Introduction
01:12 To do, In progress, Done
2:50 Trigger
4:49 Let me go
6:50 Age discrimination
7:36 WIP limits
9:43 More columns
14:27 Drive a wedge?
19:53 Blocked articles
22:30 Swimming lanes
24:10 Not fair!

———————————-
160. How to optimize your Agile Board (Kanban Board)
#agile #scrum #kanban #DevelopmentThatPays

Kanban boards, Agile boards, Scrum boards – whatever you call them, we'll go into them in detail. I'll talk about column naming, process columns, buffer columns, swimlanes, blocked items, WIP limits, card aging, everything from the basics to some pretty nifty tips and tricks. Welcome back to the shed at the bottom of the garden where we'll try out a fancy 2-camera setup for the very first time. And no: what's coming isn't a rant about physical boards versus Agile boards. Most of what I'll talk about today can be done on either, but I'll highlight 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 term for it. I think an Agile board has probably become pretty common and is often used by Scrum teams too. Surprisingly, whatever you call it, I would recommend it to any Agile team, regardless of framework or methodology. Three columns – not three swimlanes, by the way: I'll say more about swimlanes later. Three columns: To Do, In Progress, and Done. This is the only column where work gets done – you could call it an active column, I call it a process column. I'm not even sure that's the right term. If you know the right or better term, please let me know in the comments. The board is for tracking work, of course. The very first board I dealt with was one very similar to this one. It used a whiteboard with drawn columns and index cards to track individual backlog items across the board, aided and abetted, of course, by a blog from BluTak, other brands available. The second board I dealt with was printed on a large sheet of paper, with columns just wide enough for a single PostIt, and this is what the board might look like for a Scrum team if this was right at the start of the sprint. The items here are essentially the sprint backlog. That's not the case for Kanban, of course. More on that: the moment an item is picked up, it gets moved to this column to indicate that it's now being actively worked on. At this point, it's and you already know that this item should be assigned to a person. Over time, items get pulled from the to-do list and at some point items might end up in the Done column all the way. When this happens, when we're halfway through the sprint and this is still the Scrum team, the board looks pretty much exactly like 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 to generate work for this column. In Kanban things are a little different, in Kanban work pretty much dictates everything and we can activate this with another line on this [music] board, this is called a trigger point in Kanban. It's very similar to a reorder point that supermarkets and the like use to tell them that a certain item is running low and that they should order more stock and that's exactly how it works on the board. In this position there were three items left that still needed to be done. Well, there's nothing to do at the moment, but when this item gets picked up and now these two items rise above this trigger point, it's time to call a meeting and usually it takes a while to get the meeting together to do the meeting, the result of which will be more items for the to-do column and the idea behind it is that if this is the state when the meeting is called, there's enough work to keep going if it takes, say, a day or maybe ABS two days to organize this meeting, so maybe this one gets picked up in the meantime, this one gets picked up too and then finally the result of that planning meeting would be
https://www.youtube.com/watch?v=O0BnP45op0E&list=PLngnoZX8cAn9ybPBWdlydv7AaqdifaE27

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.