The resource utilization trap (pull based workflow)

An excellent illustration of pull based workflow @bradfa posted on another thread, but I felt it deserved its own.

The problem is that even in the idealized example you’re only getting 30% utilization of your very expensive software engineering headcount. From an HR department or manager point of view, software people are horribly expensive and it only gets worse if they’re only actually doing work 30% of the time.

I think this is really just a human factors problem, people think software should have huge productivity. It does but we’ve grown numb to how good it really is and the traditional “butts in seats means work being done” mindset hampers many managers.

This is an excellent analogy and easy to understand. Reminds me of git pull vs git push discussions when git workflow was being introduced to world.