1 hour ago, spivonious wrote
A planned release being behind schedule is not an emergency. It's a sign that the deadline will be missed and that the project manager screwed up.
Developers almost always get "bucketed" with the Project Manager, because ultimately it is you that provide the project manager with the data to make a guesstimate.
There are certain classes of problems where you just should not even attempt to use sprints or whatever project planning mechanism you choose. If is is a webforms/Mvc application, with a bunch of CRUD, you can more or less get the project plan right. The problem with most IT projects is that they require innovation a lot of the time, and it is much harder to quantify somebody wanting to produce an application where there is nothing on MSDN or Google or any Books.
Lets take the cloud for example, I have been interviewed where people want something like Azure with Push notifications on Android and iPhone and asking whether they think I could do it in 6 months.
Most of the time developers are too optimistic, and constantly dissapoint, by saying something is easy, and weeks or months later a task they said would take a few days is still not quite working.
All in all, I prefer working with Scientists, as typically for example, a biologist can run experiments for 3 months, and find that things just plain don't work. They accept that failure is a direct consequence of innovation, dyed in the wool, project managers consistently manage IT project with targets like people are producing cans of Heinz beans.