I think the problem is that most companies and people don't know how to use OOP programming correctly, or why it was created. You really need to read something like "C++ Coding Standards: 101 Rules, Guidelines, and Best Practices" or effective C++... or even begin here http://www.artima.com/intv/goldilocks.html. Without understanding these things completely... it becomes easy to jump on the bandwagon and dismiss the area entirely. Does anyone at these companies even know what a class invariant is? I bet most people writing class are not even thinking about writing their class as an invariant... yet its one of the most fundamental things to understand when writing good OO code. Note that I'm not arguing that everything should be written as OO, in fact that's another common miss-understanding. Understanding where OO is strong and where it is weak is key to becoming effective with OO techniques.

Looks a little like duffs device which unlike the code above was actually useful in rare cases... before compilers started to apply the optimization automatically. Oh and here's a nasty one I've actually seen:

while (1) //Who needs switch statements or else if
{
if (foo)
{
//Do stuff
break;
}

 if (bill)
 {
     //Do stuff
     break;
 }

 break;

};

We call them Stand-ups because everyone has to stand up. Believe me that makes it go faster. Also each person has only 3 major questions: 1) What did you do yesterday. 2) What are you doing today. 3) What are your blockers. This is the most important question. Normally I find that you don't have a blocker everyday. Another thing to remember is to keep the number of people down. If it gets to big you probably arn't don't agile effectively. My standups last from 5-10 minutes.