The Agile-Enterprise Innovation Planning (ÆIP) architecture is about managing radical innovation. The name originates from the combination between Enterprise Resource Planning (ERP) and Agile software development. It tries to use ERP architectural concepts but with the agility needed for innovation. The goal of the ÆIP architecture is to have Intelligence Amplification by Collective Intelligence.
The basic reference of radical innovation got expressed by Schumpeter (1975) as "creative destruction" . Prahalad (1994) have questioned why our assumptions about innovation are often wrong. The ÆIP architecture is related to the concept of (disruptive) innovation engine by Christensen (2003). The innovation literature gets expand with interdisciplinary literature. Related to socio-technical systems, we have Latour actor-network theory (1987-2005). Literature on complexity is added, like Complex Adaptive Systems of Holland (1995) and theory the complexity theory of Simon (1969-1996). For more references, see Bibliographic page.
Testing ÆIP architecture in existing development ecosystems
I found an environment well suited for participation on a socio-technical project: Drupal. Drupal is an Open Source Software Project, it was recognized in 2005 as a good software development framework and content management system for innovative web projects. For my study on radical innovation the balance between business interest and community interest in the ecosystem was essential. It allows the complexity I require to study the natural guidance to a meta-level. Drupal is still blind to its own radical nature, the Intelligence Amplifications are spillover effects, never the focus of the project. In my PhD I consider other case still in very early stage of development that is making the guidance to a meta-level more explicitly. This case emerged by the practice of Engineers in the Nederland and the conflict of their business getting lost. The pressure to adopt by innovate (or die) results in the design of radical innovation projects.