aspose file tools*
The moose likes BPM and Workflow and the fly likes Introduction to BPMN 2: process glossary Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BPM and Workflow
Bookmark "Introduction to BPMN 2: process glossary" Watch "Introduction to BPMN 2: process glossary" New topic
Author

Introduction to BPMN 2: process glossary

Yvette Schat
Ranch Hand

Joined: Dec 05, 2011
Posts: 64
Hi Jim & Ila,

What is the first thing you would do if there is nothing but regular
business supported by classic applications without any BPMN tools?

Would you map all the processes first, the most important first?

Thank you,

Yvette
Jim Arlow
Author
Ranch Hand

Joined: Mar 11, 2004
Posts: 38
Hi Yvette,

I would first identify the processes, then categorise them. A good way to categorise them is to use a Boston square:

Importance | High | Low |
...........| Low. | High|
................Risk

The best way to start is to choose a project that is high importance, but low risk. By low risk, I mean one that should be relatively to process model. The reason you choose high importance is to make the case for process modelling. So the project is relatively easy, and likely to succeed, but highly visible because it is high importance. If it was low importance, no one would care - so why bother. The worst case scenario is high risk, high importance, and this should be avoided until you are very comfortable in your modelling approach. Hope this helps.
Yvette Schat
Ranch Hand

Joined: Dec 05, 2011
Posts: 64
Hi,

I haven't done that before with the Boston square.

I guess it's preparatory work that you don't touch upon in your training course?

Kind regards,

Yvette
Yvette Schat
Ranch Hand

Joined: Dec 05, 2011
Posts: 64
I quickly gooooogled, but the hits were irrelevant.

Can you please share a link to some info on the Boston square?

Thank you, kind regards,

Yvette
Jim Arlow
Author
Ranch Hand

Joined: Mar 11, 2004
Posts: 38
No - I do not cover it in the course or book. t is not a BPMN or UML technique, just something that you use in business. There is some more information here:

www.hull.ac.uk/php/cesagh/documents/TheBostonSquare.rtf

As you can see, there is nothing to it. It is just a quick way of categorising a project in terms of risk/reward. You want a project that is low risk/high reward to begin your BPMN work.
Yvette Schat
Ranch Hand

Joined: Dec 05, 2011
Posts: 64
Ah yes, that is simple indeed.

Thank you,

Yvette
 
Don't get me started about those stupid light bulbs.
 
subject: Introduction to BPMN 2: process glossary