Best Practices Flashcards
Scope
Clearly define the scope of the Process by identifying the Who, What, When, Where and Why of your process (the Process is the How)
Start Possibilities
Identify the potential alternative ways to trigger the Process using Start Events
End Possibilities
Identify the potential alternative end states of the instances of the Process using End Events - If the ending activity are not the same, use different end events.
No. of Pages
Aim for BPMN Diagrams that fit one page
Readibility
Layout your BPMN Diagrams neatly to ease readability by minimizing flow crossing
Consistent Layout
Use consistent layout with horizontal Sequence Flows and vertical Data Associations and Message Flows
Success Path
It should be clear what the primary (“Happy”) path of the Process is
Business Rules
Whenever possible, externalize the business rules from the Process to create more concise and more agile Process models using Business Rule Tasks
Alternative Visualizations
Create alternative visualizations of the same Process for different communication purposes and stakeholders.
Phasing
Use Sub-Processes to split your Process into “phases”
Avoid Repeated Contents
Use Call Activities to re-use other Processes
Start and End
Always use Start and End Events
Alternative Instantiation
Distinguish alternative instantiation of the process as separate Start Events
End event sharing
Flows that end in the same end state should be merged to the same End Event
Mixed Gateways
Do not use mixt mode Gateways (both diverging and converging)
Activity before Diverging Conditions
Always place an Activity that will determine the diverging condition(s) just before a diverging Gateway of type Exclusive, Inclusive and Complex. A benefit of this best practice is that this decision Activity can now be interrupted if need be
Multiple diverging gateways
Abstract multiple daisy-chained diverging Gateways into a Business Rule Task
Two important criteria of a process model
Accessible (Clearly designed, users can grasp), Expressive (meaningful)
How much complex a process map should be? (For Business Users)
Better not to exceed more than 15 TASKS
Do we need message flow for message transfer or handover inside the organization?
No - We need it for between different pools
What does mean “Consistent Flow”?
A flow inside a single pool, must not be interrupted - every process in a pool can exist on its own.
Naming Convention - Pools and Lanes
Responsibilities - Roles
Naming Convention - Activity
Active verb - Short and Clear
Naming Convention - Event
Passive verb - Should not resemble an action
Straight to Success
Let the success path to be straight
Multiple Event
Not to use it
