Comment on BPMN: The Evolution of Method and Style by Kim Scott
Blog: BPMS Watch - Bruce Silver
I may be a ‘day late and a dollar short,’ and you asked for comment, so I’ll leave mine:
1) Event Gateway: I agree teaching the Receive Activity with boundary Timer is simplest, and probably covers most cases. However, I like the Event-Based Gateway (EBG) for targeting a Conditional Event, where that could occur instead of a Timer or Message Event, so its utility isn’t really totally covered by Message Activity with boundary Timer. Maybe discuss a boundary Conditional Event as well? Or maybe a footnote reference to an Appendix or something on why the EBG can be really powerful; it is a gateway that does imply controlling flow to one of the options.
2) Error Event throw/catch: I’m inclined to use Gateways instead of throw/catch errors as it’s simpler. That said, your Appendix could mention error throw/catch. 🙂
As for your other comments, I agree; BPMN could be simpler (most of my customers use ‘BPMN lite;’ a subset of the constructs), and BPMN’s single-instance (per starting token) makes things like batching ‘interesting.’ To reinforce the utility of where BPMN does apply, a ‘method and style’ guide that focuses on the 80-90% of cases sounds great!