links for 2009-06-29

  • Brandon Baxter of Lombardi: "Think about BPM as the layer between your people and your systems" – in other words, part of the functionality is to do things that your existing systems don't already do, plus orchestrate multi-system processes. This is positioning a unified UI capability as a primary driver for BPM; unfortunately, a lot of BPM implementations still do a lot of "swivel chair" integration with multiple applications still visible on the screen, due in part to deficiencies of the BPMS and part because of the lack of services/integration layers in the enterprise applications. Some good points on the value of BPM.
    (tags: bpm)
  • "Ask your analysts to provide world class requirements including functional and non-functional ones. Persude them to stay away from providing technical solutions so you can figure out how to automate your firm’s processes within the context of your SOA efforts." Excellent point on what business analysts should and shouldn't be doing. I very often see BA's delving deep into design (when they have no actual skills or experience to do so) instead of sticking to where they can add real value.

2 thoughts on “links for 2009-06-29

  1. re: unified UI as primary driver – actually i think that is taking the positioning too far. even when swivel chair is still required, BPM can be the glue that routes the work to the right person at the right time, or brings them the set of contextual process information they need to get the job done. the primary driver of value is that BPM can make the interaction of people and systems make sense, and can synthesize these disparate parts into meaningful logical processes.

    Also, as for the deficiencies – these deficiencies are more often on the side of the legacy systems rather than the BPMS tooling. And it probably doesn’t make sense to stop the BPM bus so that a legacy system can be web services enabled- when that system catches up, you can link it up to your process at that point in time (some time in the future).

  2. I said “a” primary driver, not “the” primary driver: obviously, there are others, but Brandon places a lot of stress on that point. I’ve seen a lot of deficiencies on the part of BPMS, as well as any services layer over legacy systems; maybe I’m just working with less-capable BPMS than you 🙂

Leave a Reply