What is your main reason for not meeting project deadlines?
Sometimes a project might have some hidden problems that are genuinely difficult to solve, just from an algorithmic point-of-view. However, mostly, in my experience, projects fall behind because of factors external to the programming, such as non-robust platforms/frameworks/environments, problems in defining scope, requirements that are not clear and so on.
But the most fantastic answer I've seen to this question is not mine: http://www.quora.com/Engineering-Management/Why-are-software-development-task-estimations-regularly-off-by-a-factor-of-2-3/answer/Michael-Wolfe
Other project deadlines. Less flippantly, it can be a variety of reasons, I try to ensure it isn't me but I can't promise I don't have some responsibility.
Not having the right support from people with other responsibility.
Bad estimates - usually on features that I've never coded before.
Only if the users delay in giving the required details
Shifting goal posts.... and some times it's not just the post that change, but the rules of the game too :(
Getting caught by the internet.
"Hey let's check that"
"Oh this link sounds good, let's click"
and after few hours I am still on the Internet :D
clear, what clients want.
oftenly they don't know what they want.
The spec changed too close to the deadline
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 |
<< PREVIOUS NEXT >>