Finding the Constraint

Every system, no matter how optimized, has a constraint—the point in the system that has the lowest throughput. But do you know where yours is? And what are you doing about it?    Knowing your constraint means knowing where you can make meaningful improvements to your system. Because if you make improvements to the wrong part of the system, you could actually make your flow worse (*cough, cough* hiring more developers when they're not the actual source of the bottleneck).   In this episode, learn why you should know where your system's constraint is, how you can find it, and what options you have with what to do with it.

Om Podcasten

There is a lot of material on how a team should operate in an agile manner. There is also a lot of material for leadership as to the benefits of agility, the mindset, etc. But there is not a lot of material directed towards those folks who sit in between. Agile Bites breaks down key Lean and Agile concepts and practices for the people who are often tasked with supporting these things. People who may have to be redefining their roles in a world of incremental delivery. Or maybe they’ve been put in the middle of an “agile transformation” and things are not going as well as promised.