Collaborative EAM

One key success factor for EAM initiatives is the collaboration of EA stakeholders [BBL12], since they have to provide their knowledge and participated in the transformation of the EA [RHM13]. According to [BBL12], collaborative EAM is based on three guidelines:

• “Establish a lean set of processes and rules instead of overloading the stakeholders with bureaucratic processes and unsolicited artifacts.”. This first guideline aims at fostering a lean EAM practice [BBL12].
• “Adopt evolutionary problem solving instead of blueprinting the whole future rigidly on a drawing board”. This second guideline aims at applying agile software development approaches to EAM [BBL12].
• “Foster and moderate open participation instead of relying on experts and top-down wisdom”. This third guideline aims at promoting the use of Enterprise 2.0 technologies [BBL12].

Lean Approach

The goal of applying a lean approach to EAM is to establish a demand-driven EAM process. This means, a lightweight approach is chosen by eliminating heavy bureaucratic governance concept, over-processing and other types of waste [BBL12].

Agile Approach

In software development, agile principles like Scrum and Extreme Programming are increasingly adopted by organizations [Hau+14a]. The advantages of those approaches are an increased flexibility to react to changes as well as regular communication between parties and clear assignment of responsibilities [BBL12]. Since software development as well as EAM have to handle frequently changing requirements while ensuring a close collaboration among the stakeholders, these principles should also be applicable to both [Hau+14a].

A method to enable agile EAM processes is the application of Adaptive Case Management (ACM). In contrast to traditional workflow management, ACM enables the EA stakeholders to adapt their processes at run-time. This way the highly dynamic processes of EA can be easily adapted to changing situations [Hau+14c].