Yeah. Unit tests are, to my mind, stupid. In fact, I've never been in an org that actually used test driven development. There are user acceptance tests galore, but then we have real testers who do regression testing and worry about things like security, validation, and other stuff no end user is ever going to worry about.
I'm fortunate enough to have not experienced punishment with an agile approach. With the exception of the big financial outfit I worked for last year, the other three places where i've seen in operation has usually freed up developers not to have to give constraining estimates. At the financial outfit, they practiced iterfall. Here, lets just have ridiculously complex and over detailed requirements up front, written as a "user story", and then time-box development for two weeks. Product and project managers assigned the work and never asked anyone for an estimate.
The contractors in Viet Nam, working for an outfit like the one that ran healthcare.gov, just did what they always do: worked on another assignment under the table while getting about 25% of the stuff management had committed them to out the door. But because the contracting company's front men spent a lot of time drinking with the director of product development, he was too well liked for anyone to complain. And so it went.... Everyone's been fired - in management anyway - and BigA$$ Contracting company is swindling other companies out of cash.
>--
>mjs at smithbowen.net
>http://stopmebeforeivoteagain.org
>
>The reciprocal civility of authors is one
>of the most risible scenes in the farce
>of life. -- Sam J
>___________________________________
>http://mailman.lbo-talk.org/mailman/listinfo/lbo-talk
-- http://cleandraws.com Wear Clean Draws ('coz there's 5 million ways to kill a CEO)