I wonder why - Agile goes Subterranean

I wonder why - Agile goes Subterranean

Recently I have come across several Teams, which abandoned openly working the agile way,? instead deciding to go into hiding and work underground. Quite often the teams are very good at what they do, they like it and they serve their customers well, they have just given up on the surrounding organization.

Here are some of the symptoms of Subterranean Agile:

  • Information passed to the organization is very carefully controlled and edited, transparency exists within the team but not outside. Meetings are carefully managed so that nothing rocks the boat.
  • Often a politically savvy person assumes the role of liaising with the organization. I have heard one such individual describe himself as implementing an “adapter-pattern”, making sure the outside sees what it should and the inside what it should,
  • Estimates, forecasts and statuses are tweaked before presenting them to minimize the risk of being challenged or getting into trouble. They are not outright lies, just the truth presented in its most favorable light.
  • The numbers are cooked, timesheets are often doctored to match estimates. Expenses are often recorded as something else, to avoid accountants finding something that upsets them. We have experienced several places where training courses were bought with credit cards and accounted for as travel expenses because there was no budget for training courses.
  • The team spends a lot of time obscuring what they are up to - in order to avoid being found out. This includes finding funny places to hide costs in the accounting system.
  • Team members shut up or revert to code-speak when strangers enter their territory.

Needless to say, this amounts to quite a lot of waste and is not ideal. And although it can be fun to operate under cover and see how long you can keep going without being discovered, it is not a very mature and fulfilling strategy to be gaming the system.?

But why does it happen? What causes teams to choose this path? Here are a few examples from real life.

  • First and foremost it is about control or micro-management. Detailed budget, process or documentation control are probably the biggest culprits. When bureaucratic pressure is applied to a team for any length of time there is a good chance that they will head for the mountains or go underground.
  • Fear of managers meddling with the team’s affairs. Often middle managers have very little to do, so they are looking for opportunities to get involved and exercise power over something. Teams naturally want to protect themselves from that.
  • Fear of managers snatching good people for some other work. This is known as the much-feared osprey that flaps through the team’s territory and claws an individual for another job. Better not let them know who we are.
  • The organization's overall values, vision or strategy is bogus or untrustworthy. The team just concludes “Who cares?” and they focus on their own territory, customers and collaboration and derive fulfillment and value from that.

I am sure there are many more symptoms and causes, perhaps you can supply them in the comments. It is quite common in larger organizations, and it should be a huge wake-up call to any manager worth his salt if such subterranean activity is discovered. It must be dealt with or the organization will descend into several uncoordinated tribal territories and a totally detached bureaucracy.

Robert Fujdiar

Agile org transformations, training and tools.

2 年

One of the culprits I've seen the most is budgeting. Teams not having budget "for team", but many separate budgets for salaries, trainings, equipment, parties etc. I've been (years ago) with a team that had tons of money for parties, but near zero budget for training/education outside the corporate suit of in-house trainings... Budgeting is the cause. CFO should start paying for a team, whole team, complete team and stop separating salaries/laptops/trainings/whatnot. Its easier, more transparent, and you know what you are paying for. You save a ton of money but making it easy.

回复
Kurt Nielsen

CTO and educator at AgileLeanHouse AS, speaker, and author of Liberating Organizations. DO not surrender freedom voluntarily.

2 年

Yet another "I wonder why snippet" in honor of René Jon Figgé

回复
Peter Stevens

Hey Google, It's called the Gulf of Mexico

2 年

This reminds me of the early days of Scrum - developers insisting on space to do their jobs. I read recently in a developer-centric post "Managers are going to manage." I think the issue is the only pattern most managers have for getting things done is command and control. A recurring theme among managers is how the people below them can't take responsibility (I have heard this said of VPs!). I think the problem is managers haven't thought enough about leadership and responsiveness. As a consequence there is no emphasis on leadership as a fundamental skill for all levels of the organization.

Jacob Honoré Broberg

Lead Software Engineer at Eltronic A/S

2 年

A cause could also be to avoid escalating problems that shouldn't be escalated. An example could be if someone outside the team (e.g. a middle manager) hears about a problem/bug, which sounds worse than it is - and then escalates it without the necessary background. This is sort of the opposite of green-shifting, where everything looks better when it travels through the hierarchy.

回复

要查看或添加评论,请登录

Kurt Nielsen的更多文章

  • The Fatal Attraction to Power

    The Fatal Attraction to Power

    The Situation Right Now? The recent week’s unfolding consequences of the US regime have left most of us badly shaken…

    2 条评论
  • The Case for Freedom and Responsibility in Organizations

    The Case for Freedom and Responsibility in Organizations

    50+ years ago Janis Joplin sang: “Freedom’s just another word for nothing left to lose…”. She was a wild and tragic…

  • From Hierarchy to a Network of Teams

    From Hierarchy to a Network of Teams

    Agile Lean Leadership is a framework for creating a sustainable and resilient networked organization as an alternative…

    61 条评论
  • A Lesson in Engagement

    A Lesson in Engagement

    This is the story of a journey of many months through unknown territory together with a couple of departments in the…

    2 条评论
  • The Challenge of dismantling SAFe

    The Challenge of dismantling SAFe

    Yet another essay in the Statler and Waldorf series. Statler and Waldorf have left their balcony and instead of looking…

    6 条评论
  • The Challenge of Agile Orthodoxy

    The Challenge of Agile Orthodoxy

    Yet another essay in the Statler and Waldorf series In this series of articles, we have come to a point where Statler…

    2 条评论
  • The challenge of Power

    The challenge of Power

    Yet another essay in the Statler and Waldorf series. We are examining the consequences of basing an organization on…

    10 条评论
  • The challenge of the traditional hierarchy

    The challenge of the traditional hierarchy

    This is the first essay in the Statler and Waldorf series. One of the most frequent challenges people report when…

    4 条评论
  • Ukrainian personal reflections – unplugged

    Ukrainian personal reflections – unplugged

    In the 6+ weeks since the Russian invasion of Ukraine, we have experienced a shattering of almost every belief in…

    3 条评论
  • Are you predictable?

    Are you predictable?

    How does uncertainty and risk affect you? We have often heard people say “Well, that was predictable” and it’s usually…

    4 条评论

社区洞察

其他会员也浏览了