Requirements hybrid: How to master the balancing act between waterfall and SCRUM with requirements management
The field of Requirements Engineering and Management (RE&M) is also important in modern times for the successful execution of projects – project management requires the specific procedures and techniques of RE&M in order to be able to establish the project requirements in such a way that all project participants have a common understanding of the requirements. The Pulse of the Profession® 2014 study came to the conclusion that this mutual cooperation is important, but that it is not yet predominantly applied:
According to the study, only 49 percent of all projects examined had the resources to apply the RE&M discipline correctly.
Only one third of all surveyed project managers regard RE&M as critical for their project
Even 53 percent do not use a formal process for requirements analysis
Based on these figures, is it at all surprising that major projects such as Berlin Airport are delayed due to non-compliance with special requirements? No – and that is why it becomes clear that even in agile and iterative project management, cooperation with the RE&M discipline cannot be dispensed with.
Problem: Bridging inadequacies of traditional approaches with agile approaches
However, while in traditional approaches, such as the waterfall model, the requirement specification is usually made at the beginning in order to allow the complete project planning and solution specification to be connected based on it, agile and iterative approaches (hereinafter referred to as agile project management, from which the term hybrid project management must be distinguished) differ considerably.