Organizations want to be efficient. That’s why we have specialists doing specialized work. Unfortunately, specialists doing specialized work means that we end up with dependencies. Specialist B can’t do her work until Specialist A finishes his. And Specialist C is waiting on both of them. In the software world, this looks something like this:
— Michael Stump (@michael_p_stump) April 15, 2016</blockquote>
A lot of organizations use a board like the one pictured to manage those dependencies. They chart out the dependencies and plan around them. Sticking with our previous example, C does his or her work first, then B, then A finally finishes up the work.
While managing dependencies like this is minimally functional, it’s not ideal. In fact, it should be your last resort. What happens if B or C gets delayed? What if there are other people waiting on all of that work? What if we’re under a time crunch? Our real life work flow reflects the messiness of the picture.