In this post by Sandy kemsley, where she reports about the Gartner BPM summit I have found some interesting ideas upon which I would like to react. She speaks about the talk by Janelle Hil at Gartner's BPM summit, where Janelle Hill reminds why BPM is different from workflow and business process reengineering techniques that existed before. She also discusses when the use of a BPMS becomes necessary. What I found most intriguing is that she speaks about policies on the level of BPMS (I guess she means generally also modelling and analysis frameworks) , and I am convinced of the necessity of managing policies at the same level of managing process, organizational, and system information. Policies can also influence the business by making it do what is expected from it, having influence on its quality, performance or security among others. So policies represent an asset for the enterprise in the same way processes do.
Another interesting thing to note is that Gartner just changed their definition of BPMS so the new quadrant looks different. the final and most interestingthing in the post to me was discussin process design patterns. Sandy kemsley says that the approach she uses with clients is trying to identify what kinds of process patterns they have in order to decide for the best BPMS for them. "three most common patterns that they see with BPMS are case management, form-driven workflow, and participant-driven workflow". Janelle Hill has listed 6 of them, which I would be curious to know.
Marwane El Kharbili.