Hybrid process models allow the use of traditional process models using agile methods, to more flexibility, to achieve higher quality, faster time-to-market and also.
In the past, many process models have been often applied dogmatically by using the “Process First” model. Legacy models (like the waterfall model) are based on this paradigm and have been enriched in the last years and they have become “process monsters” (see unified process for example).
Starting with the 90’s a couple of alternative approaches appeared and resulted finally in the Agile Manifesto in 2001. Starting from here the pragmatic approach has higher precedence over processes. Recently even this approach became dogmatic; only agile approaches are the right ones and non agile approaches are “devil speech” even if this is against the base paradigm of the Agile Manifesto.
In recent time alternatives appeared which try to combine classical and agile approaches. Advantages from both methodologies can be joined and agile methods can be used in classical waterfall based environments. The hybrid approach is established in several projects/relationships for several years now and increased quality and time-to-market.
Essential parameters of the hybrid process are accepted uncertainties and options in the requirements phase that will pass the contract phase and are resolved during (agile) development. In addition there’s the possibility to enhance/change the need during the development phase, even if the classic contractual part does not allow those kind of interactions.
More Information can be found in the blog.