zlacker

>>vimes6+(OP)
Alternate view point - driving projects to a specific deadline allows the other departments in the company to coordinate marketing, packaging, and selling the product. These people don't sit on their hands patiently waiting for engineers to finish building, their work can take many months just as the development does, and sometimes also involves making tradeoffs to deliver on time. No company wants to wait another year after development is finished before they start earning money for it.

>>danpar+V7
Furthermore, financial penalties on late delivery are not uncommon in enterprise business-to-business settings. These penalties are sometimes quite steep

If the choice is between releasing kinda-working, but unpolished software, or throwing a developer's monthly labor cost out of the window every single day, these management anti-patterns suddenly make much more sense

>>thow-0+Qo
I business agreement isn't an arbitrary date. Those dates should be clearly communicated to engineers.

>>Forge3+Pp
They are communicated to engineers - in the form of deadlines...

>>danpar+xz
Problem with a lot of deadlines is that you aren’t told if this is a hard requirement because of a contract or some other external factor or just an ego trip or wishful thinking of upper management.

I have seen it plenty of times that management pushed for an arbitrary deadline. The deadline passed, project was not done and nothing bad happened other than another new deadline.