One other possibility is that this developer is experiencing schedule chicken. I'd recommend reporting your time estimates to your lead, giving it the old colle

One other possibility is that this developer is experiencing schedule chicken. I'd recommend reporting your time estimates to your lead, giving it the old college try, but going home at reasonable times and not pushing the clock too hard. In some large organizations (I've seen this previously where I worked), the first group to claim that the schedule was unreasonable became the scapegoat for slashing of features. So, everybody would look around and try to get a sense of who was furthest beyond making it and not say anything unless their team was the long pole, since you'd "benefit" from the increased schedule time anyway without the high-visibility hit for failing to deliver. Yes, totally dysfunctional. But, in some orgs, it may be the most realistic (or at least typical) way to save the scope of the project.