Nine Outrageous Things I Learned At Think Tank

  1. BPM is about empowering people. It was co-opted by integration vendors, who took it down an IT-centric path. ? Connie Moore, Forrester. [Note: Forrester has separate analysts and ?waves? for human-centric and integration-centric BPM. Guess which is Connie?s?]
  2. The ultimate goal of BPM is self-aware processes that can recommend changes to process owners. ? Connie again. [Yeah, I hear businesses asking for that all the time.]
  3. Portability of process templates was never a goal of BPEL, just interoperability [i.e., abstract process definition]. ? John Evdemon, Microsoft, BPEL TC co-chair. [You mean I?ve been defending BPEL against the haters all this time for nothing??]
  4. BPEL is not ready for production. ? Evdemon [Because the 2.0 spec could still change in the next 30 days? At least I hope that?s it?]
  5. BPEL probably got more press than it deserved when it came out because of the vendors supporting it. I probably should be covering up my badge. ? Evdemon again [At least the guy?s honest! Note: BizTalk 06 still doesn't support it except as an import/export format.]
  6. OMG can?t finalize the metamodel (BPDM) and schema for BPMN until it works out the complete semantics of choreography (message exchange patterns between multiple collaborating processes). ? Fred Cummins, EDS, OMG BPDM TC. [Translation: don?t hold your breath?]
  7. The BPDM metamodel and BPMN schema are available today. It?s called XPDL. ? Keith Swenson, WfMC XPDL TC. [That?s basically true. OMG has effectively given XPDL a two-year window to establish itself as the de facto BPMN schema, and make the official OMG epic irrelevant.]
  8. An easier way to do BPM is to just use modeling and BAM, and forget the process engine and BPMS. That would make it easier to "sell" internally. - Consensus of BPM practitioners at my roundtable. [D'oh!]
  9. My blog posts are too long. Who has time to read 500 words? - Sandy Kemsley, BPM blogger. [I have no comeback to that one.]