The Incremental Commitment Model (ICM) was presented in 2006 in a paper titled Using the Incremental Commitment Model to Integrate System Acquisition, Systems Engineering, and Software Engineering written by Barry Boehm (Spiral Model) and Jo Ann Lane, a Principal at the University of Southern California Center for Systems and Software Engineering. The ICM model emerged primarily […]
Are Your Requirements Good or Just Good Enough?
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 […]
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 […]
Achieve Unqualified Project Success
In 1995, the Standish Group’s Chaos Report said, “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 222%” In 2004, the same group’s Chaos Chronicles reported: Only 34% of projects expected to finish on time; 52% had proposed functionality; 82% […]
Recent Comments