Efficient BPMN: from Anti-Patterns to Best Practices

Transcription

1 Efficient BPMN: from Anti-Patterns to Best Practices Architecture Made Simple Kristina Bigelienė, No Magic Europe

2 About Speaker Kristina Bigelienė Solution Architect for Business Modeling domain at No Magic Europe (Lithuania). Practical experience in BP analysis, modeling, optimization and implementation of ERP systems. Telecommunications (TeliaSonera group) and Higher Education (private University) business domains. OMG certified expert in BPM. Master degrees in Computer Science and Management. 5 years of academic teaching experience. 2

3 Why Modeling? Understand WHAT and HOW are you DOING Preserve KNOWLEDGE Manage COMPLEXITY Business process analysis and implementation SUCCESS highly depends on the QUALITY of the created business model! 3

4 State of BPM Practice Business process modeling practice is not yet mature. Common modeling mistakes make models non-understandable. Stakeholders are not accepting modeling as diagrams are too complex and inconsistent. 4

5 Challenge of Informal Business Process Drawings How to optimize the service time for the VIP customers? 5

6 BPMN: Standard for Business Process Modeling BPMN stands for Business Process Model and Notation. Provides a standardized graphical notation for business process modeling. Is understandable by all stakeholders: business analysts, excellence people, developers. BPMN 2.0 standard is developed by OMG (Object Management Group): 6

7 Modeling: From Anti-Patterns to Best Practices Share and Apply Best Business Modeling Practices! COMMON MISTAKES BEST PRACTICES Different Business Process Understanding Inconsistent Naming Large Process Diagrams Modeling Minor Details Slalom in Diagrams Re-inventing Bicycle Unified Business Process Understanding Strict Naming Conventions Multiple Layers of Detail Documenting Minor Details Clear Primary Scenario Applying Process Patterns 7

8 Different Business Process Understanding AUTHOR BUSINESS PROCESS DEFINITION Geary A. Rummler & Alan P. Brache A series of steps designed to produce a product or service. If the result is directly of benefit for the customer, it is a primary process; otherwise it is supporting process. Martin Ould Workflow Management Coalition (WfMC) BP Trends A coherent set of activities carried out by a collaborating group to achieve a goal. A set of one or more linked procedures or activities that collectively realize a business objective or policy goal, normally within the context of an organizational structure defining functional roles and relationships. At its most generic, any set of activities performed by a business that is initiated by an event, transforms information, materials or business commitments, and produces an output. Value chains and large-scale business processes produce outputs that are valued by customers. Other processes generate outputs that are valued by other processes. 8

9 Unified Business Process Understanding Business Process is a reusable set of related activities which is performed by an organization in order to create business value (product, service, document) leading towards achieving organization s business goals. Can you define a clear beginning?... a clear end?... the business value process brings?... a set of composing activities?... a reusable sequence of activities? Examples: Provide Loan Fulfill Order Organize Conference Prepare Annual Budget Handle Incident Report Perform Financial Audit Recruit New Employee 9

10 Modeling: From Anti-Patterns to Best Practices Share and Apply Best Business Modeling Practices! COMMON MISTAKES BEST PRACTICES Different Business Process Understanding Inconsistent Naming Large Process Diagrams Modeling Minor Details Slalom in Diagrams Re-inventing Bicycle Unified Business Process Understanding Strict Naming Conventions Multiple Layers of Detail Documenting Minor Details Clear Primary Scenario Applying Process Patterns 10

11 Anti-Pattern: Inconsistent Naming Mixed naming hides inconsistent understanding! 11

12 Strict Naming Conventions The language that we speak shapes our thinking Emphasis on the achieved result, not on action! No conjunctions in names! Short name + documentation instead of long names! Activities: a strong verb + a noun (e.g. Announce Seminar) Participant: a noun (e.g. Delegate, Seminar Coordinator) Events: a noun (e.g. Registration Request, Registration Deadline) Data objects: a noun (e.g. Customer List, Feedback Form) Gateways: unnamed - gateways do not perform work! Sequence Flow: named only after a data-based (Exclusive and Inclusive) gateway, gives a condition on which it is activated (e.g. Participants > 30) 12

13 Best Practice: Refactored Process Diagram Action names focus on achieving the result. Unnamed Gateway. No conjunctions in names. No long names: details are moved to documentation. Recommendation: to establish naming convention guidelines. 13

14 Modeling: From Anti-Patterns to Best Practices Share and Apply Best Business Modeling Practices! COMMON MISTAKES BEST PRACTICES Different Business Process Understanding Inconsistent Naming Large Process Diagrams Modeling Minor Details Inconsistent Loop Usage Slalom in Diagrams Re-inventing Bicycle Unified Business Process Understanding Strict Naming Conventions Multiple Layers of Detail Documenting Minor Details Defining Right Scope for Activities Clear Primary Scenario Applying Process Patterns 14

15 Anti-Pattern: Over Complex Process Diagrams 5±2! 15

16 Best Practice: Multiple Levels of Detail 16 Rule: up to 10 activities in a single diagram. Question: How many tasks can we define in 3 levels of detail?

17 Modeling: From Anti-Patterns to Best Practices Share and Apply Best Business Modeling Practices! COMMON MISTAKES BEST PRACTICES Different Business Process Understanding Inconsistent Naming Large Process Diagrams Modeling Minor Details Slalom in Diagrams Re-inventing Bicycle Unified Business Process Understanding Strict Naming Conventions Multiple Layers of Detail Documenting Minor Details Clear Primary Scenario Applying Process Patterns 17

18 Anti-Pattern: Modeling Minor Details All models are wrong but some are useful. W. Edwards Demming We can always add more and more business rules to the diagram. Is it worth putting it all to a diagram? 18

19 Modeling: From Anti-Patterns to Best Practices Share and Apply Best Business Modeling Practices! COMMON MISTAKES BEST PRACTICES Different Business Process Understanding Inconsistent Naming Large Process Diagrams Modeling Minor Details Slalom in Diagrams Re-inventing Bicycle Unified Business Process Understanding Strict Naming Conventions Multiple Layers of Detail Documenting Minor Details Clear Primary Scenario Applying Process Patterns 19

20 Anti-Pattern: Slalom in Diagrams Slalom a lack of consistent direction of flow. Reading BPMN diagram is obscured by: Long, meandering, crossing lines. Different size boxes. Jumping in a timescale. Mixed flow of the primary and alternative scenarios. 20

21 Best Practice: Clear Primary Scenario Primary scenario should be visible on one line ( ). It is recommended to start modeling from primary scenario and add secondary scenario(s) later. All activities are the same size. Shapes are aligned. 21

22 Modeling: From Anti-Patterns to Best Practices Share and Apply Best Business Modeling Practices! COMMON MISTAKES BEST PRACTICES Different Business Process Understanding Inconsistent Naming Large Process Diagrams Modeling Minor Details Inconsistent Loop Usage Slalom in Diagrams Re-inventing Bicycle Unified Business Process Understanding Strict Naming Conventions Multiple Layers of Detail Documenting Minor Details Defining Right Scope for Activities Clear Primary Scenario Applying Process Patterns 22

23 Anti-Pattern: Re-inventing Bicycle There is no delay to wait for the answer There is always 1 month delay 23

24 Process Pattern: Deferred Choice Process patterns provide bigger modeling components that enable creating simpler and more efficient process diagrams. 24

25 Process Pattern: Timer Events Patterns Scheduled Start: Delay: Timeout: 25

26 Process Pattern: Internal Business Error (1) 26

27 Anti-Pattern: Repeating Event Repeating events complicates diagram and its maintenance. 27

28 Process Pattern: Attached Event Pattern A SubProcess with attached event allows defining the scope of an event precisely. 28

29 Wrap Up: Refactor Your Models Use standard notation Apply naming conventions Refactor large diagrams to several layers of the details Exclude minor details from diagrams Apply process patterns Keep primary scenario clear Create good looking process diagrams! 29

30 Building Sustainable Business Modeling Culture Use business modeling standards like BPMN. Stick to a set of principles for efficient modeling. Apply best practices for modeling and model management. Learn and apply process patterns (blueprints). 30

31 The Recipe for Success think BIG start SMALL and EVOLVE 31

32 Improving business models is a never ending journey 32 Thank you!