2 ms·
The why is typically: 1) The person(s) doing the estimate aren't qualified to do so. 2) There is a disconnect between wishful thinking and reality. 3) There
by chiefalchemist 8y ago
The why is typically:
1) The person(s) doing the estimate aren't qualified to do so.
2) There is a disconnect between wishful thinking and reality.
3) There is some arbitrary future milestone (i.e., "We need to ship by ____ because ____ is happening the following week.") that is independent of software development.
4) Most importantly, when the deadline is missed the estimate / estimators are not questioned, the software team is.
I've been at this a long time - too long? - and the narrative that IT is __always__ at fault is a myth that needs to be buried.