Ask Slashdot: Development Requirements Change But Deadlines Do Not? 221
cyclomedia writes "Over a number of years my company has managed to slowly shift from a free-for-all (pick a developer at random and get them to do what you want) to something resembling Agile development with weekly builds. But we still have to deal with constant incoming feature changes and requests that are expected to be included in this week's package. The upshot is that builds are usually late, not properly tested and developers get the flak when things go wrong. I suspect the answer is political, but how do we make things better? One idea I had was that every time a new request comes in — no matter how small — the build gets pushed back by 24 or even 48 hours. I'd love to hear your ideas or success stories. (Unfortunately, quitting is not an option)"
Agile? (Score:5, Funny)
Re:Make a deadline for additions (Score:5, Funny)
I go upstairs to the salesman who promised that feature to the customer without changing the deadline, grab him by his shirtcollar, and tell him, "You worthless overpaid coke-addled dumbfuck...if you ever, ever pull that shit on me again, you'll be explaining to the customer why you're talking like a soprano and walking like a cowboy."
-- Ethanol-fueled
Re: Agile? (Score:5, Funny)
Typically, you start working er'ly in the morning. And stay at it till the even'n's glomming.
-- MarkusQ
Re: Agile? (Score:4, Funny)
What DO you do with a drunken sailor?
Maybe your experience is different but I was never put in the hold with the captain's daughter. Either that or she needed a shave and I wasn't interested in holding the mirror. It was a long voyage though.