I think good project portfolio management is an essential discipline for software development.
You have to know what you want to do, why you want to do it (in terms of measurable benefits), how much it is likely to cost, know who will do it, know when it will be done, how much it ended up costing, and how much benefit actually was realised.
Then you have a defined pipeline of work, and software developers wake up in the morning knowing what they are supposed to be doing.
Enter the villain.
Our villain has a vague, but very senior role. He is responsible for improving something or the other, and is brimming with vision, personality and the gift of the gab. He has no time for pipelines. His ideas are hot, relevant and need to be done now! (Before he forgets them or moves on to the next grand scheme)
Our villain likes to pick on vulnerable teams, all smiles, and uses his charm and lofty position to lure or bully them into his cause. He gets things done. Under the radar.
He is dangerous.
He needs to be taken out.