REThink 4.0

Requirements engineering is a crucial part of the success of a project. We have known that for decades. Nevertheless, many projects still fail due to problems with requirements. It is time for a different type of requirements engineering: rethinking and adopting a new paradigm

Requirements are often neglected in projects. They have an unagile, bureaucratic feel, and the rush-to-product syndrome puts the focus on tasks that create "real" outcomes, that is, visible, working product parts and features.

On the other hand, projects fail because they spend too much time on requirements. In the end, you do not sell a perfect requirement specification. Only the product counts. As always, the world is not black and white.

On the new engineering playing field, a fundamental problem with requirements is the strong focus on text. That makes it nearly impossible, and, in any case, takes a lot of effort to manage hundreds or thousands of text fragments in a complex and dynamic environment...