The frustration caused by trying to work on an ExtremeProgramming project, when it goes wrong on a social level.

''Because we can deal with technical problems within the system, right?  So the social problems are outside the system.''

I think EdYourdon''''''s DeathMarch is one of the best books I've ever read on this subject. -- rad

ExtremeFrustration is

* Joining a project so full of bugs you can't even compile and run the code you're supposed to work on.

''No, ''joining'' the project was Extreme''''''Stupidity.  You should have applied the principles in QualifyingEmployers. The feeling you get from ''staying'' on the project is ExtremeFrustration.''

* Getting off of a project that you didn't much care for to work on something fun, only to be repeatedly dragged back for FireFighting.
* Getting some badly needed personnel assigned to your project, only to have them repeatedly dragged back to fight fires.
* Being forced into maintaining 200 000 lines of undocumented, "comment free" results of CowboyCoding. Especially when you joined to work on something else.
* Joining a project that is desperately needed and thoroughly funded but nothing can be produced because no one will stop analyzing and tell you what they need.
* Getting blamed by users for crappy software when you are the single person in an IT department innocent of all blame because you have been advocating refactoring the damn mess for a year.
* Having all technical decisions made by the least technical person, then being force fed their incompetence, then getting blamed for the resulting poor quality.
* You FixBrokenWindows, but two more break every time you do.  Nobody else on the team will help you fix them; they're too busy "making progress" on getting the project OutTheDoor.  Bonus points for getting into trouble for wasting time, because they don't understand what you've fixed.
* You ActInsteadOfComplain to ChangeYourOrganization, go over the head of the PointyHairedBoss, and discover PointyHairedBossTransitiveClosure. ''(YouJustCantWin)''
* ReleaseEasyReleaseOften doesn't happen.  You have the final release coming up fast, and there is no one person on the team who can put all the code and data together to make it.

----
ExtremeFrustration caused by MicrosoftProgrammerMentality on your team can lead to PickingAtScabs.

Frustration and the stress that goes with it can cause BurnOut.  I'm realising that this is where I am now.  It's not funny.  ''See PositiveNegativity''