Deadlines on programming tasks that are meant to create a little pressure inevitably slip because they don't mean anything real. Deadlines that *are* real might slip because programming takes as long as it takes, and knowing that it has to happen before a certain time doesn't really do anything to help that.
There are two ways you can deliver more quickly in programming: reduce quality expectations or cut features. Suggesting the former is a good way to get a swift kick, and the latter will result in long meetings about what features are the most or least essential. Basically between schedule, budget and features, you only get two. If you have an absolute deadline, then you need to choose whether you also have a fixed budget or a definite required set of features.
Mokalus of Borg
PS - If it's features and budget you need, it's going to take some time.
PPS - And if it's a fixed budget and schedule, you might not get all your features.