I like the Idea, but Disagree with one Conclusion
Time for a Process Manifesto? , picks up some ideas from the Agile Manifesto:Jacob Ukelson, in his post
So far so good. But then he draws the following conclusion:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
I think that traditional BPM does less well on the first two principles – it is pretty clear that comprehensive documentation (the process model) is still a basic requirement. Probably because of the mindset – process and tools take precedence over individuals and interaction. So not so good on those fronts.I guess people have different notions of what “traditional BPM” is. The traditional BPM I’m familiar with is not about documentation, it is about working software (and so it is not clear that comprehensive documentation is a basic requirement). The diagram is the process, and the diagram actually runs. Although, I’ll admit I came into the BPM world via Lombardi, and brought with me software and consulting approaches learned from other jobs. So I might have missed out on the specific traditional BPM Jacob is referring to. But in our (BP3) world of BPM:
- People are the focus
- Document if it reduces risk or adds value. Don’t document just to pass gateways.
- We emphasize working software and feedback loops. Luckily the software tools we use reinforce this approach and support it.
- We use the term “value-driven vs. plan driven” but I think it substantially has the same spirit as “collaboration over contract negotiation”.
- Responding to change over following a plan: of course, see the previous point.