Scrum is like 20th Century Politics (Part 2 of 3)

Part 1

Having toiled for years under the yoke of a brutal waterfallocracy, one bitter developer learns of management's decision to adopt scrum and sees...a revolution.

Born is the Marxist, leader and friend to the common bit farmer.

The revolutionary swoons at scrum's commitment to the "self-organizing team". He visualizes an enervated bourgeois middle management, an empowered development base that directs company affairs, and an opportunity to play video games at work.

Of course corporations are a little different than governments in that the workers cannot throw out their bosses and forcibly wrest control of the organization. However, under the guise of scrum doctrine, the proletariat can confuse and befuddle the established order in an organization to the point where they feebly hand him the reins of power.

How is this done?

Guerrilla warfare is waged through deception and surprise. The revolutionary arms himself and his comrades with all manner of scrum books and training documents. Prepped with a preponderance of process techniques, the team can then confront management's every proposal with a counter proposal of their own that is "more scrumlike according to so and so".

If management wants estimates in hours, the team will stubbornly insist on Fibonacci numbers. If one week sprint cycles are proposed, the team will produce evidence suggesting that three weeks have been used effectively elsewhere. Ultimately, the goal is to take advantage of management's unfamiliarity with scrum. If the stakeholders and upper management can be convinced that the team actually knows what they are talking about, the revolution has been a success. With luck, the team will be granted control to run the process. The people have won!

But as is the case with most revolutions, the new establishment must take steps to ensure that they do not lose the power that they were so recently awarded.

The process changes that the team originally dreamed up to wage their revolution are calcified into a rigid, inflexible doctrine. Non-conformity is met with oppression (sarcasm), and team members who question the power structure are sent to the Gulag (ignored). Productivity decreases as creativity is squelched, and the lack of actual work being done results in frequent kitchen raids and food lines, which in turn lead to shortages and empty shelves. Work days become cold, bleak, and hard. Members of the collective are encouraged to spy on their comrades and report deviances such as frequent trips to the bathroom. There is little laughter.

In the end, the developer population loses power so that a few can maintain it.

There is a balance between the top down and bottom up forms of control described in Part 1 and Part 2 of this series. This is called responsible elected representation, which we will visit this in Part 3.

Comments

[Bradley Johnson]

Hi Richard- I enjoyed reading your reply. You've shamed me into wondering why I didn't finish the series. After considering this, I can only present my excuses 1. I didn't think anyone was reading 2. I too began to doubt the capacity of humans to reconcile power. 3. Sometimes I am lazy.

I've met many selfless people in my software career, but they were generally not identified by management as having "leadership qualities". The philosopher king is usually recognized posthumously by other misunderstood bookworms, none of whom hold real power themselves.

Newly inspired to write part 3.

P.S. Check out this thought-provoking article about the reason that scrum sometimes fails to work in a consulting context http://bit.ly/2Ta0pp.

[Chesterton]

I'm disappointed that you never cranked out Part 3 of this series. I've seen tastes of your first 2 versions of scrum-ocracy first hand. I've even witnessed a 3rd version - I'll call it oligarchy - in which expert consultants - perhaps the "industrialists" in your perspective - convince management to grant them tight control for benevolent purposes of "restoring order." To minimize chaos, they limit participation in development. In-house developers are relegated to irrelevance with "busy-work", while the elites carry on sort of a "private scrum". Meet the new boss . . .
So I wonder, is the "responsible elected representation" version of scrum that you describe truly sustainable? As politcal history demonstrates, human nature seems to demand that every form of power distribution eventually devolves into vortexes, between which power struggles are inevitable. The power-holder forgets higher purpose and lapses into power-hoarding...perhaps even convinced that his way is necessary to survival of the group.
But, as you've stated, corporations are not like governments - they generally don't belong to the employees - and even the most well-intentioned of managers must do what they think fosters the long-term viability of the enterprise . . . regardless of what that means for the morale of employees. In the "oligarchy" I described, it appears that management may have made the best decision for near-term payoff, but long-term consequences could include costly dependence on the consultants' "foreign oil".
In the end analysis, maybe this whole discussion is moot from the employee standpoint. Perhaps it's best to simply mind your own business: "Jobs are owned by the company, but You own your career!" (Quote from Earl Nightingale)