You’ve got a quick job to do so fire it off to an IT team. It should only take around half a day of effort so you expect to hear back by the end of the week. Three weeks later and you’re still waiting. So why is this happening? What is the deal with IT delays?
Apologies in advance to all scientists, engineers, and mathematicians.
This is going to be another opinionated piece on the ideal line management reporting structure for an Agile team. I’m not going to get into organisational hierarchy or connections between teams, instead just focusing on the Agile team itself. This does, however, relate to the concept of dependencies.
Over this series, I’ve spoken in detail about the organisational impact of IT dependencies in your system. I’d like to take a diversion and discuss how it can impact the individual.
I posit that even without the work benefits you could derive from eliminating dependencies, the quality of life changes you could bring about would more than pay for the effort.
This isn’t an article about workplace stress, we’re all pretty familiar with its cost to our economy. Nor is this an article about the cost of employee churn. It’s not even about the cost to productivity through disengagement. Let’s move forward knowing the impact of people not being happy.