Requirements management for applications pays off!

 

In large software projects, requirements management can account for 20 per cent of development costs. A systematic and disciplined approach to definition, documentation, maintenance and tracking makes sure that the requirements of a software project are defined, documented and maintained throughout its entire life cycle. This ensures that the developed application meets the actual needs of users and the company, and that project goals are achieved. Effective requirements management is fundamental to successful software development, helping to avoid costly rework and misguided developments. This makes it a critical success factor for any project.

Due to the financial implications, it is becoming increasingly common for companies to review their requirements management. This involves answering the following questions:

1. What is the standard market share of requirements management in the total cost of a software development project?

A look at our comparative data from benchmark projects shows that standard market values for requirements management range from five to 20 percent of total development costs. The average value across the data in the Metrics Data Lake is 12.97 percent.

2. What role does requirements management play in the success of software development projects?

Stringent requirements management has a positive impact on project success. This refers to the achievement of project goals in terms of quality/function, time, and cost/budget.

3. What are the consequences of having either too little or too much requirements management?

An analysis of the database shows that comparatively little requirements management is associated with high testing costs. Therefore, it is generally advisable not to cut corners to avoid costly misunderstandings. Available benchmark data reveals an interesting correlation: the more time invested in requirements management, the lower the subsequent testing costs.

4. Are there 'optimal proportions' for requirements management?

Decreasing testing efforts: On average, projects with less than five percent of their resources spent on requirements analysis require just under 39 percent for testing. This suggests a significant degree of repetition in testing. In projects where more than 25 percent of resources are spent on requirements analysis, however, the value for software testing drops to below 20 percent.

Efficiency gains in implementation: Interestingly, projects with a high requirements management share (30–35%) require significantly less implementation effort – an average of 17% – than the overall average. Here, the implementation share is 27 percent.

Optimal range: The data indicates that the optimal range for expenditure on requirements management is 15 to 25 percent, where the overall efficiency of the project (with a focus on design and development activities) is highest.

 

These findings lead to the following specific recommendations for action:

• Early Bird: Investing in the early stages of development projects is worthwhile. The data clearly shows that investing in precise requirements at an early stage avoids the need for more expensive corrections and unnecessary iterations later on.
• Balanced approach: Too little requirements management (less than 10 per cent) usually leads to excessive testing efforts, while too much (more than 30 per cent) may not offer the optimal level of efficiency.
• Rethinking quality assurance: Rather than planning extensive testing phases, project managers should consider allocating more resources to the requirements phase to improve overall quality. Concepts such as test-driven development, where tests are defined during the requirements phase, can be helpful here.
• Requirements refinement as a continuous process: Even in agile projects, the continuous refinement of requirements should be considered a critical activity, not an optional extra. Otherwise, there is a risk that the project will descend into trial and error.

Effective requirements management is not an unnecessary bureaucratic process, but rather a means of minimising risk and investing in project success. This is because the cost of troubleshooting increases exponentially the later in the project cycle issues are discovered. Our comparative data from application benchmarks clearly shows that careful planning and analysis at the outset saves time, money and resources in the long run. Depending on the specific functionalities to be developed, I believe that a requirements management share of between 15 and 25 per cent strikes the best balance between precision and efficiency for most projects. This insight should be incorporated into strategic project planning to ensure the long-term success of application projects.