|

The dangers of outdated requirements - and what you can do about them

Outdated requirements

Nothing is more frustrating than realizing after hours of work that the basis of a paper was outdated. When this happens in a review, it's annoying. However, if it is the expensively paid work of a supplier who has created a component based on outdated requirements, then this can drive a small company to ruin.

Event information: systems.camp North on 20.10. in Hamburg, Agile Systems Conference (ASK) on 24/25.10 in Munich,  Modeling Craftsmanship "South" on 3.11. in Friedrichshafen.

These are just two of the dangers posed by outdated requirements. But what can we do to avoid such dangers from the outset?

Root cause analysis

There are many reasons for outdated requirements and, accordingly, many different measures. What is more, this does not only apply to requirements, but also to many other system and product development artifacts.

One of the most common causes is copy & paste. Although there is a legitimate use for it, copying is a measure that can solve problems quickly - and cost us dearly later on.

With copy and paste, many problems are solved quickly - and cost us dearly later on. [tweetthis]With copy and paste, many problems are solved quickly - and cost us dearly later on[/tweetthis].

This is not just about reusing fragments or sentences of requirements. In principle, sending a requirements document around by email for a review is also a copy & paste operation. This is only acceptable if it is ensured that the review results are merged again in a timely and disciplined manner. But this is rarely the case. And since there are enough alternatives today, sending documents for reviews is now considered criminal.

Cheap alternatives are wikis, or online document systems such as Google Docs. If you want more convenience, you can use systems such as the Jama Review Center fall back

Single Source of Truth

Ideally, there should be a central data repository in development that can be used without copying. In software development, this has long been practiced in the form of code repositories. This option has also been available for requirements for decades, although the corresponding systems are generally quite expensive. However, especially when developing complex products in a team, word has gotten around that appropriate data storage is indispensable.

However, the older tools for the professional management of requirements are often isolated solutions. As long as work is carried out in the system, all is well with the world. But the moment the data has to be processed elsewhere, it has to be copied again. This can be solved with processes, but this is time-consuming and error-prone, so it is important to declare at least one data source as the "original". Changes may only be made there.

Here, too, there are convenient solutions. With integration hubs, data can be automatically and reliably be synchronized between different tools. In this case, the fact that it was copied is not a problem.

Settle debts

In software development, there is the term "Technical debt." This refers to the costs incurred as a result of poor or short-term implementation. These must be compensated for in the future. If this is not done, the problems accumulate. So when we send a review document by e-mail, debts are incurred. These must be settled by the disciplined feedback of the review results.

Technical debt does not only exist in software development, but in all development [tweetthis]Technical debt does not only exist in software development, but in all development[/tweetthis]

Working with requirements creates all kinds of debts. Paying these is no fun, but it is important. For example, orphaned elements must either be reassigned or deleted. However, in order to be able to do this, we need a well-maintained traceability. Maintenance is also part of repaying the debt.

Describe problems

Even if it should be a matter of course by now: Good requirements describe problems, not solutions. Technical solutions in particular have a habit of becoming outdated over time. So anyone who specified a VGA connection ten years ago, and not an "interface to an output device", is now dealing with an outdated requirement - without anything necessarily having changed.

Similar Posts

Leave a Reply