The short life of requirements presents especially smaller companies with organizational and economic challenges. The constant change of desires and demands on a project or product during its development phase is now often part of everyday life of an IT company in software development.
In order to be able to meet customers and quality requirements without too high a cost jump, an adaptation in the procedure of the project implementation must take place.
For a structured requirements engineering, an orderly process is indispensable to efficiently and effectively offer products or services – especially in a global market, where time-to-market and stakeholders are critical success factors.
Incorrect communication already at the beginning of an order usually entails the following consequences only in the later process, which then lead to high costs for the service provider, which can not be economically compensated.
The so-called “10 rule of error costs” states that the costs of avoiding or eliminating errors increase by a factor of ten in each phase. The costs of errors that are not detected and remedied at the time of planning, but only in the later phases such as conception or implementation are thus exponentially higher. An IT project can only be successful if, in addition to the IT development effort and thus the planned resources in a defined period of time in the agreed quality, as well as the IT production costs and thus the downstream follow-up costs considered. Particularly critical is the observance of the production costs already at the planning period because of the highest cost causation, whereas the cost development and thus the becoming visible of the associated costs only become apparent afterwards.