Hit your Deadlines
Sometime it feels that for a lot of companies working in software development, deadlines are something that should be kept a bit vague, a bit ‘could be this week, or could be next week’. I would like to propose an immediate end to this!
Deadlines should be stuck to, as rigorously as end-of-term papers in college. In college, missing your deadline means losing marks or possible even a fail. People try it once or twice in their first year in college, get badly stung and then learn how to hit deadlines. We in the software development industry should behave in the same way.
The excuse is often, ‘oh the client changed their minds halfway through’. Obviously, this can mean a lot of different things but here’s how I propose it should affect the deadline… Whatever was agreed upon in the original delivery schedule and remains unchanged, should be delivered according to the original deadline.
Whatever has been affect by changes should be isolated and a new delivery schedule and deadline should be agreed upon. This new deadline may even be on the same day as the original deadline. However by isolating the areas affected by the client’s change request, everyone can quickly see how much work is involved in the changes, which of the original tasks are now eliminated, which new tasks are added and what the dependencies are in terms of the original tasks.
Based on this information the new schedule can be agreed upon and the deadline can be set. No deadline should be missed. Simple! 🙂