[icedchai]

This is all true. I worked in a medium size (400+) fully "agile" organization There was constant short term thinking and seemingly nothing was properly designed or actually engineered.

External facing APIs changed regularly, affecting other teams and leading to slow and painful integration. By regularly, I mean just about every sprint. How about thinking more than 2 weeks ahead?

It didn't help that there were lots of inexperienced guys just out of college (who probably thought this was normal.) Along with a "manager" with extremely poor communication skills (not uncommon in development) this was basically a disaster.

We did, however, have lots and lots of unit tests. We spent about half of each "iteration" rewriting them due to the API problems.

I gotta laugh.

[spronkey]

Sounds like a problem with the organisation and engineers. Unless of course the externally facing APIs had to change regularly because of requirements changing, in which case welcome to software development, you were probably lucky that those external APIs weren't an opaque box for six months like they may have been without an agile methodology.