As an operational definition, good requirements are cohesive, complete, consistent, correct, feasible, modifiable, necessary, prioritized, reusable, testable, traceable, verifiable and unambiguous. If requirements aren’t captured to this high standard, rework or project failure is the natural consequence. No one will ever get good requirements that meet this standard by walking into a room and asking […]
Archives for 2011
Who’s to Blame for Troubled Projects, IT or the Business?
There is enough empirical evidence to say that poor requirements contribute to the majority of project failures. Look at these study conclusions published over a 13 year period beginning in 1995: Requirements problems have been proven to contribute to 20-25% of all project failures. The average project overran its budget 189% and its schedule by […]
Recent Comments