A technically-clueless master of bullshit and bureaucracy-surfing.
A graduate of DilBert University trained to insinuate himself between the big shots above and the grunts below. See IEEE Software Sept/Oct 1998 p.18.
See Also: PointyHairedBosses, CaptainHornHair
Sometimes used as a DramaticIdentity here on WardsWiki.
Some PHBs will drive you to work for the competition. When you announce you are leaving, they might just throw a chair across their office, and emit an obscenity-laced tirade implying they are going to "bury" that competition. See http://www.theregister.co.uk/2005/09/05/chair_chucking/ for the incident that inspired this paragraph.
The value of this tactic in retaining the employees needed to accomplish that "bury" UserStory using clean code (instead of dirty tricks) is currently a matter of debate.
You can "bury" the competition literally with dirty tricks (ie, have them rubbed out), or you can "bury" them figuratively by producing a superior product. The "UserStory" thing is just an extension of the metaphor, I think. In any case, chair-throwing is not the way to accomplish it, and is a symptom of acute AlphaMale TestosteronePoisoning?.
Kiss-up traits of a PointyHairedBoss:
Pretend they understand tech, but they don't
specifically: Says all the right things, at every meeting, for months, until you are completely off your guard, and then one day wham the hammer falls. The question "What's a 'UnitTest'?" is a veil for "why are we paying you to write unit tests when everyone else is fixing bugs like they are supposed to?" and so on...
MicroManagement prevents you from doing X, even though it's very low risk and will improve things. But you know you can get permission to do Y, and quietly piggyback X on it. Even though Y is much higher risk. eg: adding covariant return types to the java language by introducing generics.
"I better not catch you wasting time reading that danged Wiki again. It's giving you notions!"
All the symptoms of you obeying his dumb orders show up in your performance review.
"If you were a team player, you would stop adding all those tests that fail on your colleagues' workstations."
"Don't give me any crap about DailyBuilds. We have too many CodeForks. A total rebuild would take too long."
"Don't give me any guff about our CodeForks. To fix them, everyone would have to set up CommonBuildEnvironments, and that would slow them down from working on our next feature."
"I only understand practices A, B, & C, but not their complementing practices X, Y, & Z. So I'm going to relentlessly micro-manage you on the former, then complain when you go off schedule."