Thursday, 6 January 2011

Annotated Bib.: Risk management in the bpm lifecycle


 

[1] M. zur Muehlen and D. T.-Y. Ho. Risk management in the bpm lifecycle. In C. Bussler and A. Haller, editors, Business Process Management Workshops, volume 3812, pages 454–466, 2005.

 

This paper provided an overview of risks associated with BPM projects during all the phases of the BPM lifecycle. The paper started by trying to define BPM, providing different definitions by different researchers, and finally defining BPM as creating “alignment among the individual process components input, output, resources, process structure, and process goals”.

Then it went in to defining risk and risk management; it explains that risk management composed of 3 main phases: identification, analysis, and control of risk. Also explained 4 of the management strategies toward a risk; mitigation, avoidance, transfer, and acceptance, by giving a definition and example for each of these strategies.

 

Then in section 4 went into “risks specific to BPM projects”, and listed common risks encountered in and between BPM lifecycle phases; it listed six phases of BPM life cycle, and four transition phases, in each of these ten phases listed a number of a BPM-specific risks to this phase.

 

This paper focused more on risks that can occur during BPM lifecycle and not on integrating risk to BPM or producing a risk-aware BPM. It showed and pointed out risks that might occur during the BPM life cycle.

Relation to research in hand, this paper might not be directly related to the research in hand, as it is not concerned with integrating risks, it was set only to point out risks associated with each phase of BPM life cycle. But it could be useful in showing the importance of considering risks, and other security aspects from the beginning, as these risks pointed out in this paper can be used as example and show case to prove that risk could happen and we should be prepared for it by considering it from the beginning and considering what kind of reaction to take.

No comments:

Post a Comment