Everyday Kanban

Discussing Management, Teams, Agile, Lean, Kanban & more

Month: March 2013

Visualization tips for Kanban cards

Below are some common things you want to see on kanban cards and some suggestions about how to visualize them.

Type of task
If your team works on varied types of work, use different colors for the cards based on the type of work it is so that it is easy to differentiate at a glance.

Have laminated small avatars or pictures for each person. Attach the avatars to cards to denote assignee.

Continue reading

Midnight thoughts on capacity, slack and WIP

What’s more than 140 characters but less than my normal tome? This blog post 🙂 Its midnight here in Seattle and my brain is still whirring about topics stirred up at Lean Coffee this morning. So, I just wanted to throw some quick thoughts down on virtual paper regarding capacity, slack and WIP. Here goes…

Look, managers (and I can say this to you, because I’m a manager too). It’s about flow, not capacity. What I mean is that the measure of success is not ensuring that developers are busy every single minute. Rather, its improving your system flow so you get more done in less time. The problem is that people think to do the latter, the former must be done. Beware! It can have the opposite effect.

In addition, that 15 minutes at the foosball table or 10 minutes playing with nerf guns can be crucial to those with jobs involving complex thought work. The brain needs time to process information. A developer who is actively coding 100% of the time is likely not doing their best work. Now, team, if you’re reading this, I’m not signing off on 4 hour sprees in the game room!

This morning a topic was how to get developers to buy into WIP limits. I can say with certainty that my experience proves that WIP limits are analgesics for workers. More focus breeds better quality features completed faster and THAT equals less stressed developers. Who doesn’t want that?

Kanban in the wild: Restaurants

My last post about Kanban in the wild was focused on Disney World. For this case study, we are going to look at the standard restaurant. But, first, a key…

Case study key

  • Dining parties == Task/User Story/Issue
  • Waiting List == Backlog (usually with estimated wait times listed)
  • Reservations/Call Ahead == Special class of service for task/user story/issue (eg. expedite/fixed date)
  • Tables == In Progress Dining groups (WIP limit applied)
  • Bussed & Cleaned table == Deployment
  • Cycle Time == The length of time you are seated at the table
  • Lead Time == The length of time you are in the restaurant (waiting + seated)

Continue reading

© 2024 Everyday Kanban

Theme by Anders NorenUp ↑