Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
Businesses Programming

Ask Slashdot: Development Requirements Change But Deadlines Do Not? 221

Posted by Soulskill
from the anonymous-emails-and-heavy-drinking dept.
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)"
This discussion has been archived. No new comments can be posted.

Ask Slashdot: Development Requirements Change But Deadlines Do Not?

Comments Filter:

The only problem with being a man of leisure is that you can never stop and take a rest.

Working...