How to properly punish developers for missing deadlines?

Question

Project management

In a company, the development department often does not meet the deadlines that it itself determines and approves. There are hundreds of reasons for this. As for the "carrot" for the delivery on time - it's understandable. There is a bonus in the form of% of the project and all sorts of additional goodies. But what to do with the "whip" is unclear. How to punish correctly so that there is no demotivation, but it is clear that you need to plan more correctly?

Answer 1

Well, you will start punishing developers, they will start naming deadlines like a month for tasks for a week.
It's one thing when the work is template, done many times (as, say, a typical site), in this case, all the terms can be estimated more or less accurately. Another thing is when something unique and not template is created, the error can be many times.
I would advise two or three times a week to find out from everyone what he did the previous days, what problems he has, what solutions he sees, in order to see in real time how the assessment and the situation are changing. But yes, here it would be desirable to understand yourself at least at an average level in order to understand what it is all about.

Answer 2

The boiler
UPD:

So Agile is designed to track this crap.

Answer 3

The one who meets the deadlines - they just inflated them for you.
The greater the punishment for failure, the more the term is blown up.
It can reach sloppiness, which can only be controlled by observing the employee.
We use the practice of blowing up deadlines, but with control. We control traffic, we have a number of prohibited sites (time eaters), and we control the arrival and departure from work. This is enough as a preventive measure against laziness and busyness in the wrong place. Managers get their weekly activity report on Friday and can decide over the weekend who should get caps on Monday.
Those who go at 9:30 and leave at 17:30 and have lunch for 1.5 hours receive acc. % salary at the end of the month. Number of working days * 8 - the amount of tracking in the office or remotely for those who are a persistent violator.

Answer 4

Well, a person is not a robot, everyone has the right to make a mistake, sometimes everything is done by 90% and bang a mistake with which you can sit all day ...
I would ask like this: how to reduce the likelihood of missed deadlines?

Answer 5

Any punishment is demotivation. Even verbal mumbling. Did you allow for an error in the calculations, or did you simply approve the named terms "as is"? If yes, then I have bad news for you. You need to mortgage 20% -50%

Answer 6

It is necessary not so much to punish, but to control more carefully, so that at an intermediate stage it can be seen whether he has time or not.
Fails - overtime. You can even pay for overtime separately if the reasons for the delay are convincing.
A few overtimes, but projects delivered on time - and the developers will better think over their deadlines.

Answer 7

Damn, well, how to punish)))
As in 50 shades of gray)))
there will be 50 shades of development)))