Column 2

James Kobielus on "Process Mining: Because Your Company’s Workflow Issues Aren’t Always Obvious". I saw some interesting research on this at BPM2009, and am seeing it manifest in some products like Fujitsu's process discovery tool. Lots more work to be done here.

Good look at why you should be modeling your decisions separately from your business processes. By denoting a task as a decision (in BPMN, that would be a business rule task), it links either implicitly or explicitly to a decision model, which in turn is based on rule families. Underlying all of this is the necessity of getting business rules/decisions out of process models for maximum agility.

A simple set of steps for getting started with a BPM project. I disagree with the first step, on how to identify and select a business problem: I think that you should pick something that is mission-critical, since it guarantees that the BPM project won't be marginalized. Keep the initial implementation simple, but pick a process that really matters to the business.

An interesting piece on business architects by Nick Malik. He points out that the job is not trivial, it's not the same as a business analyst, and if your manager doesn't understand the mandate and role of a business architect, you're in trouble.

Bruce Silver's comments on yesterday's BPMN 2.0 Update webinar with Robert Shapiro (which I covered in a previous post). He has some great comments on interoperability, especially how the subclasses help with that in spite of OMG's avoidance of any tool interoperability compliance tests.