You'd expect the BPM-savvy practitioners and evangelists such as found on LinkedIn's "BP Group" to be able to easily come up with a good definition of BPM . A specific and actionable definition. You'd be wrong.
In a BP Group forum discussion entitled "Can Anyone Make One Sentence Describing BPM", most of the answers were generic and non-actionable and often sounded like mission statements -- the kind of feel-good mission statements that are ridiculed by cynical business writers -- or worse the statements were self-referential ("BPM is about improving your processes"). In fairness. participants shared many worthwhile insights. It's just that the there was a general and disappointing failure to answer the question in a useful way.
Let's look at what would be a good top-level definition of business process management -- and then why a good definition is important.
On the forum, Kenneth Beard came the closest to a good description of BPM with his "scientific management of work activity to enable informed decision-making", although I would make the case that final phrase in this definition is outside the scope of a definition of BPM.
Your host proposed the that BPM can be simply defined as "the modelling and management of repetitive work", which is certainly not original, but this concise definition emphasizes a fundamental concept, specifically the centrality of the question of work to the definition of BPM.
Dynamic BPM, along with Adaptive Case Management, is the name given to a growing body of practical knowledge about building better software for business process. The trouble with much of existing BPM is that poorly done, the implementation of BPM can contribute to a reduction in organizational flexibility. The wags have it as "pouring concrete over your business" -- as if enough concrete wasn't already there from the acquisition of ERP systems. It's fair to say that no one is to blame for this -- and ER . . . read more