Business Process Management (BPM) is complex, expensive, and often fails! If you agree (in the year of 2012+), then you should read the following rules to do BPM correctly in your next project.
I have written an article for “Service Technology Magazine” regarding the following topic: Lessons Learned: Best Practices for a Successful Introduction of Business Process Management (BPM).
Here is the link: http://www.servicetechmag.com/I64/0712-3.
The article illustrates some rules how to do BPM correctly. These rules are very important for success of a BPM project. If you do not consider them, your next BPM project may fail too…
Here is a short summary for introducing BPM succesfully (for people who are short of time and not reading the whole article):
- Rule 1: If you want to do BPM correctly, then be aware that your primary goal is to improve Business-IT-Alignment!
- Rule 2: If you want to do BPM correctly, then do not try to realize it without a service-oriented Architecture!
- Rule 3: If you want to do BPM correctly, then be aware that BPM is not just tooling, but an engineering process with a huge, iterative lifecycle!
- Rule 4: If you want to do BPM correctly, then use it only when you really gain benefits!
- Rule 5: If you want to do BPM correctly, then do NOT believe in BPM myths!
- Rule 6: If you want to do BPM correctly, then use BPMN 2.0!
- Rule 7: If you want to do BPM correctly, then choose the right BPM tool for the job!
- Rule 8: If you want to do BPM correctly, then do NOT use it for systems integration!
Please leave your feedback, if you have any other opinions or experiences.
Follow
